Fix problems `type` in `reject-event` payload

Description of the bug:

When zustelldienst rejects submissions automatically the type in the problems array doesn't match the regex pattern from the Security Event token Schema.

❌ Is:

• Problem type for reject-reply events automatically created by zustelldienst is https://schema.fitko.de/fit-connect/submission-api/problems/automatic-reject-of-submission

✅ Should:

• Problem type for reject-reply events automatically created by zustelldienst is https://schema.fitko.de/fit-connect/events/problems/automatic-reject-of-submission

Environments:

all environments (DEV, TEST, STAGE, PROD)

Additional Information:

• Open Code Bug: https://gitlab.opencode.de/fitko/feedback/-/issues/60
• SET schema: https://docs.fitko.de/fit-connect/docs/set-schema/overview (see https://schema.fitko.de/fit-connect/events/reject-submission → problems → type → pattern)

Component:

• zustelldienst

Contact persons including contact details:

• Open Code Bug: https://gitlab.opencode.de/fitko/feedback/-/issues/60

Checklist:

• Add Severity label
• Add team label
• Related/affected issues/stories/epics linked and explained in the bug issue
• Creation of an automated test
• Bugfix deployed on DEV
• Bugfix tested on DEV
• Bugfix deployed on TEST
• Bugfix tested on TEST (possibly also by the connection project itself)
• Successful fix reported to Team Operations (Teams channel)
• Bugfix deployed on STAGE
• Bugfix tested on STAGE if necessary
• Bugfix deployed on PROD
• Bugfix tested on PROD (possibly also by the connection project itself)
• Final communication by Team Operations if necessary
• Internal documentation was checked and updated if necessary
• External documentation has been checked and updated if necessary
• Updated changelog if necessary

Approach/Solution:

• Fix the test by asserting the correct type value: https://git.fitko.de/fit-connect/zustelldienst/blob/main/src/test/java/de/fiep/zustelldienst/securityeventtoken/service/EventLogWriterServiceTest.java#L210
• Fix the implementation and use the BASE_PATH for the PROBLEMS_URL - not the API_BASE_PATH

Release version of the artifact: