Chef CLI 0.1.5: New Initial mapping system

The main focus of this release is a new system of managing initial domain mappings.

Instead of promoting a single blueprint as the initial domain mapping of the org, there is now a separate screen for reviewing the current initial domain mappings, and the blueprint of the latest test import can be 'merged' into it, enabling:

• multiple possible targets, with the end-user deciding in the main DevRev UI how to map. For example it is now possible to encode a mapping like '"task" in the external system may map to issue or ticket in devrev'
• mappings applying to record type categories

Two new transformation methods are added:

• Mapping to custom stages
• Mapping permissions

Some features that don't have good E2E support in airdrop are removed:

• Mapping to custom objects
• Selecting a existing devrev record for anything but parts

Some bugs are fixed:

• The behavior when changing a fields mapping to "use devrev record" requires editing the default id filled in is made less confusing by not filling in a full default id.