feat(api#95): Remove encryptedData and encryptedMetadata from the response when submitting a submission

Closes #81

* The "old" Destination is now in destination-any but still called Destination.
* There is now a PublicDestination (w/o contactInfo and callback) and a PrivateDestination
* Removed notice about missing fields depending on scope (since its now obvious from the schema)

Reasoning: It't not version 20 but version 2.

According to RFC 2616 (HTTP), the POST method is used to create a *new subordinate* of the resource identified by the Request-URI. In contrast, PUT is used to store the entity under the Request-URI.

Instead of the /status ressource, the /info ressource can be used instead

400: useless for a GET request
401: handled by API-Gateway

Resolves: #55
Resolves: #58