Configuration Import of External Data Store

issue background:

Certain AM Configurations must be imported in order

While working to separate application configuration in a separate store from our CFG config, customer noticed that some of the configuration needed to be imported (via amster) in an exact order while the documentation does not call that out.

Customer had to import in order:

• all global configs
• top realm DataStoreInstance config
• top realm DataStoreService config
• all other Realm configs
• sub-Realm specific DataStoreService configs
• Realm Applications

RFE request: 

It would be preferable to not need to import configurations in specific order or have documentation on different configuration dependencies. Customer solution added some complexity to our deployment/build scripts as well as our repository