Configurable Persistence of Additional IDs in AKTIN DWH

**User Story**
As a hospital operator, I want to configure which additional IDs from the HL7 CDA document (encompassingEncounter/id) are stored in the i2b2 database of the AKTIN DWH. This will allow me to attach specific, institution-relevant identifiers (e.g., emergency service number or waiting room triage ID) to patient records for later analysis.

**Examples:**

- A hospital in Berlin wants to store an emergency service number with the dataset to better track emergency patients.
- A hospital in Freiburg wants to store a waiting room triage ID with the dataset to analyze waiting times and triage priorities.

**Requirements**
Ability to configure in AKTIN DWH which additional IDs from encompassingEncounter/id should be persisted.
Support for multiple ID types per dataset (e.g., up to three to five additional IDs).
Flexible definition of relevant root values, allowing each hospital to specify the IDs relevant to them.
Storage of configured IDs as separate columns or attributes in the i2b2 database.
Ensuring traceability of IDs through documented mapping (e.g., via metadata or a mapping table).

**Benefits**
Increased adaptability of AKTIN DWH to the specific requirements of different hospitals.
Improved tracking and analysis of emergency patients by storing additional locally relevant identifiers.
Avoids unnecessary storage of irrelevant IDs, allowing targeted configuration based on each institution’s needs.