fix: Add /.well-known/jwks.json to API

See merge request fit-connect/api!100

refactor(submission): Refactor announcedContentStructure to announcedAttachments

See merge request fit-connect/api!99

Closes #92

Closes #81

feat(FCON-155): POST must have no <uuid> in path

See merge request fit-connect/api!97

Einheitliche Verwendung von LeiKa-Schlüssel vs. LeiKa-ID

See merge request fit-connect/api!94

Marco Holz authored 3 years ago and Jonas Gröger committed 3 years ago

Die mit '99' beginnende Zahlenfolge, die eine Leistung im LeiKa
eindeutig referenziert, wird als LeiKa-Schlüssel bezeichnet.
Zusätzlich gibt es zu jeder Leistung eine LeiKa-intern verwendete
LeiKa-ID.

Die Bezeichnungen wurden in der API entsprechend auf LeiKa-Schlüssel
vereinheitlicht.

FCON-155: Make .../keys endpoint POST (new key!)

See merge request fit-connect/api!96

feat(FCON-155): Add PatchDestination class to Schemas

See merge request fit-connect/api!95

api: typos

See merge request fit-connect/api!93

feat(destination): Add key endpoint for adding or getting destination JWKs

See merge request fit-connect/api!81

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