Migration to 7.11.0+

Changes

New environment variable to define default anonymization time:
- TS_DEFAULT_ANONYMIZATION_TIME_IN_DAYS
New environment variables to configure the ticket anonymization scheduler task:
- TS_TICKET_ANONYMIZATION_SCHEDULER_ENABLED
- TS_TICKET_ANONYMIZATION_SCHEDULER_CRON
- TS_TICKET_ANONYMIZATION_SCHEDULER_LOCK_MIN_DURATION
- TS_TICKET_ANONYMIZATION_SCHEDULER_LOCK_MAX_DURATION
Static resource for "Anonymization Configuration" is created, resource id is "urn:com:bosch:bci:tm:ts:Anonymization-Configuration"
An application role called "Ticket Anonymization Configurer" is introduced, which has read, add, modify and delete privileges for configuring anonymization.
The user requires the role "Ticket Anonymization Configurer" to call the following endpoints:
- PUT /BCI_TS_ADMIN/v1/{tenant-id}/anonymization-configurations
- GET /BCI_TS_ADMIN/v1/{tenant-id}/anonymization-configurations
Static resource for "Anonymization Task" is created, resource id is "urn:com:bosch:bci:tm:ts:Anonymization-Task"
An application role called "Ticket Anonymization Executor" is introduced, which has execute privilege for the anonymization task.
The user requires the role "Ticket Anonymization Executor" to call the following internal endpoint:
- POST /BCI_TS/v1/{tenant-id}/tickets/anonymize
  Example request body:

{
    "userId": "dd5c8775-b1c3-4441-ad53-0055a660b441",
    "createdTime": {
        "from": "2023-12-15T23:00:00Z",
        "to": "2023-12-31T23:00:00Z"
    },
    "closedTime": {
        "from": "2023-12-15T23:00:00Z",
        "to": "2023-12-31T23:00:00Z"
    }
}

None of the parameters in the request body are mandatory. Use the appropriate combination of parameters that fits best to your use-case.
If an empty request is sent, the anonymization configuration of the tenant will be used for computing the closedTime (i.e. the request will have the same effect as the scheduled anonymization task).

New environment variable to define default archiving time:
- TS_DEFAULT_ARCHIVING_TIME_IN_DAYS
Static resource for "Archiving configuration" is created, resource id is "urn:com:bosch:bci:tm:ts:Archiving-Configurations"
An application role called "Ticket Archiving Configurer" is introduced, which has read, add, modify and delete privileges for configuring archiving.
The user requires the role "Ticket Archiving Configurer" to call the following endpoints:
- PUT /BCI_TS_ADMIN/v1/{tenant-id}/archive-configurations Example request body:

    {
      "archivingTimeInDays": 30
    }

Example response body:

    {
      "ownerTenantId": "a80d483c-522e-11ee-be56-0242ac120002",
      "archivingTimeInDays": 30,
      "updatedBy": "502d43fe-c916-11eb-b8bc-0242ac130003",
      "updatedTime": "2023-01-31T23:00:00Z"
    }

GET /BCI_TS_ADMIN/v1/{tenant-id}/archive-configurations
- New environment variables to configure the ticket archiving scheduler task:
TS_ARCHIVING_SCHEDULER_ENABLED
TS_ARCHIVING_SCHEDULER_CRON
TS_ARCHIVING_SCHEDULER_LOCK_MIN_DURATION
TS_ARCHIVING_SCHEDULER_LOCK_MAX_DURATION