Tokenise appliance specific data on export/import

Tokenise appliance specific configuration on export so that import can use those tokens and substitute-in destination appliance configuration.

Currently a limited number of resources may be tied to the platform on which they exist on export. Exporting their configuration and then importing to another platform would require the data be amended manually.

Idea is to try spot this type of data at export, so it can be tokenised, and a subsequent import can read the tokens and replace them with appliance specific configuration values.

Example/Use case(s):
Option lists. It is not uncommon for REST option lists to access the Morpheus API via the appliance.
The appliance URL will be hard coded in the exported scribe resource, so will need to be amended on the new appliance.