feat(FCON-243) Stricter validation for callback and email

See merge request fit-connect/api!92

feat(api): FCON-151: submissions for pickup

See merge request fit-connect/api!90

fix(destination): differentiate between public and private destination

See merge request fit-connect/api!89

* 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.

feat(api-86): Multiple regions per service

See merge request fit-connect/api!88

Introduces multiple regions per service.

https://git.fitko.de/fit-connect/api/-/issues/86

FCON-205: remove send:destination:<id>

See merge request fit-connect/api!87

docs: add externalDocs element to API spec

See merge request fit-connect/api!86

feat(FCON-189): rename 'schemas' to 'submissionSchemas'

See merge request fit-connect/api!85

this rename is done to have a more specific name for the field. just
having the generic word 'schema' might be confusing.

Fixes #83

The `externalDocs` element allows referencing an external
resource for extended documentation. Since we do it, lets
refer to it.

refactor(event-log): Migrate the status from submission to event-log

See merge request fit-connect/api!84

Event-Log fixes based on integration tests

See merge request fit-connect/api!83

FCON-204: Remove CaseJWK / DPoP

See merge request fit-connect/api!82

Vereinheitlichung des Leistungs-Identifikators

See merge request fit-connect/api!80

Replace POST by PUT in submit-application endpoint

See merge request fit-connect/api!36

Angleichung Service-ID und Schema-URI in Beispielen

See merge request fit-connect/api!78

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.

Im Metadatenschema und in service-type.yml wird die URN einer Leistung im Attribut `identifier` hinterlegt. Dementsprechend sollte die Leistungs-URN auch in einem Zustellpunkt als `identifier` hinterlegt werden.

Nicht mehr existierendes Attribut `otherIdentifiers` aus Beschreibung entfernt.

See merge request fit-connect/api!79

Die Beispiele zur Schema-URL sollten zur angegebenen Service-ID (Leika-ID) passen.

Zum konkreten Beispiel, siehe: https://fimportal.de/suche/%3FsearchWord=blaue;karte;eu%26L=1%26D=1%26P

Fix examples and remove history

See merge request fit-connect/api!76