GitLab

- assume mas-dt context rather than soar context
- makes it easier for us to think about the project

- either individual properties or geojson
- add geojson test

+ move all schemas into formats
+ add test messages for semver, commit ref and branch

- Use soar charlie zone as example of inclusion/exclusion zones

- geometries are geojson features
- classified with an instruction to the automation

- revert changes to emergency schema
- remove Feature and FeatureCollection

The destination field contains a publish topic
You don't send to the autonomy engine
You publish a message on a topic that the autonomy engine
is subscribed to.
The send/receive field is confusing.
The aim was to give clients the option to subscribe to
all messages from platforms or all messages to platforms
but it's unclear how to use this for things like the
configuration message.

I've updated the messages and schemas so that all
messages pass validation with the js validator