Update electronic manifest service

[dpgraham4401]

🚀 Feature Request

Add a service to the haztrak back end for updating a manifest in e-Manifest.

Designing the REST endpoint, I'm not sure what is a better approach.

1. /api/.../manifest/{mtn}
2. /api/.../manifest/emanifest/{mtn}

We are currently implementing the 2nd option for our emanifest create (POST) service. If we implemented the same for the update service the endpoint design would looks as follows:

/api/.../manifest/{mtn} would update the haztrak database but not e-Manifest.
The opposite would be true for /api/.../manifest/emanifest/{mtn}. This would be nice because it would provide a clear separation of duties. The endpoints would always returns the same schema/resource definition (/manifest/{mtn} would return a Manifest JSON object, /manifest/emanifest/{mtn} would return a information about an asynchronous task launched to update e-Manifest).

further research required