BiDiKo: Replies must have the field `encryptedData`

Submissions and Replies without machine readable data are not supported (we do not allow attachment-only submissions/replies in order to promote machine readability). Therefore, the field encryptedData / authenticationTags.data has to be required for Replies.

The following endpoints are affected:

• PUT /relies/<id> → encryptedData*
• GET /relies/<id> → encryptedData*
• PUT /relies/<id>/accept → authenticationTags.data*

Akzeptanzkriterien

1. Field encryptedData has to be required for endpoint PUT /relies/<id>.
2. Field encryptedData has to be required for endpoint GET /relies/<id>.
3. Field authenticationTags.data has to be required for endpoint PUT /relies/<id>/accept.

Durchführungsplan (von Entwickler:in bei Umsetzungsplanung auszufüllen)

• adapt submission-api accordingly → fields must be marked required. → submission-api!173 (merged)
• update validation in zustelldienst to verify that fields are set. → https://git.fitko.de/fit-connect/zustelldienst/-/merge_requests/303
• Update api-tests accordingly. → https://git.fitko.de/fit-connect/zustelldienst/-/merge_requests/239/diffs?commit_id=648255aabe7c1f8101846a8856cff6c62d11d95e
• Release new release candidate of submission api → 1.3.0-rc4