Remove canned, hard-coded data for elements of the system and instead define default data via REST calls

[osowski]

Instead of having hard-coded data across multiple microservices that requires synchronization, remove all initial data / state from the microservices (fleets, ships, voyages, containers, cities), and instead define this state via a series of REST calls following deployment. This would allow for multiple pre-canned 'scenarios' with different fleets, voyages etc.

This can be done via a Job-based implementation for the deployment as a whole or as part of the individual microservices Deployment with an InitContainer.