Migration to 7.10.0+

Changes

New environment variables to define log levels:
- LOG_LEVEL_ROOT
- LOG_LEVEL_BOSCH
- LOG_LEVEL_TM
- LOG_LEVEL_LIQUIBASE
- LOG_LEVEL_HIBERNATE
- LOG_LEVEL_SPRING
- LOG_LEVEL_SPRING_SECURITY
- LOG_LEVEL_SPRING_WEB
- LOG_LEVEL_SPRING_TRANSACTION
- LOG_LEVEL_SPRING_JPA
- LOG_LEVEL_PORTAL_CLIENT
- LOG_LEVEL_MMPD_CLIENT
- LOG_LEVEL_MACMA_CLIENT
- LOG_LEVEL_SECURITY
- LOG_LEVEL_LIFE_CYCLE
Static resource for "Solution Group Filtering" is created, resource id is "urn:com:bosch:bci:tm:ts:Solution-Group-Configuration"
An application role called "Solution group configurer" is introduced, which has add, remove, modify and read privileges for configuring solution-groups.
The user requires the role "Solution group configurer" to call the following endpoints:
- PUT /BCI_TS_ADMIN/v1/{tenant-id}/solution-group-configurations
  Example request body:

    {
       "enableSolutionGroupFiltering": true
    }

Example response body:

    {
        "tenantId": "a80d483c-522e-11ee-be56-0242ac120002",
        "enableSolutionGroupFiltering ": true,
        "updatedBy": "502d43fe-c916-11eb-b8bc-0242ac130003",
        "updatedTime": "2021-01-31T23:00:00Z"
    }

A new Application Role "Ticket Modifier" is created to allow modification operation on any ticket, without being restricted by the fine-grained-access-control implementation related to Condition Monitoring use case.