Add support for an external UX

[otter42]

There are a couple changes to the core which will be needed in order for an external, user-centric, UX to functional against its API. Based on conversations with @jdweeks I have started building out a loosely-coupled ux project which can function as a drop-in replacement ux for that provided by the core. Ideally it will be integrated via a docker-compose file and the basic internal-ux will be targeted more towards simple use cases and administrators of the Mockiato core.

In order to achieve this we need to add CORS support in the core as well as a few enhancements to the planed authorization model. Ideally we would also add the ability for the ux to save specific meta-data with the entities which the core may not care about or be aware of. There are a few patterns we can use to accomplish this. Lastly there will be some related enhancements to the code entities and matching methodology which are exposed through the new ux.

Let's find a time to connect over WebEx. We are at the point where we need to sanity check the plans and make some of the core enhancements to enable the externalized ux.

[otter42]

this is a simple add of the following...
npm install --save cors

then in the app.js
require('cors')
...
app.use(cors)