Merge in RED/persistence-service from bugfix/RED-6468 to master
* commit 'a2feec73e65115063366223e4347e60f5fcf37cf':
RED-6468 - Exception in persistence service for DownloadCleanupJob (very rarely) - changed the lazy loading to eager for dossier in download status entity
Merge in RED/persistence-service from bugfix/RED-6548 to master
* commit '47df255e12a67059bf9f318fe03756ea15fa0d28':
RED-6362 - Cannot add KMS signature - rework after review
RED-6548 - Username not saved / Email saved as username - extend createUserRequest with username - update the username with the one provided - update also the username in case of updating profile with a new email address
- extend createUserRequest with username
- update the username with the one provided
- update also the username in case of updating profile with a new email address
Merge in RED/persistence-service from RED-5504-message to master
* commit 'd92409dadbeb8a48a377d079a5d49ac6d0476d43':
RED-5504 - Prevent using exact same database schema/buckets/index for multiple tenants - extract the name of the unique constraint
RED-5504 - Prevent using exact same database schema/buckets/index for multiple tenants - update the sql messages
- update saveDigitalSignatureKms signature
- move the convert from DigitalSignatureKms to DigitalSignatureKmsEntity to the service
- remove the magicConvertor which cause problem for the certificate
Merge in RED/persistence-service from RED-6523-ui-multitenancy to master
* commit 'd8d37170667996f08ed2c31e507a278c4d9533f8':
RED-6523 - ui multitenancy issue for dev realms
Merge in RED/persistence-service from RED-5504 to master
* commit '663770bf9b262c30af3f5c9ccf034bea65100dc2':
RED-5504 - Prevent using exact same database schema/buckets/index for multiple tenants - remove tenantsHostAndSchemaMap - update junit test
RED-5504 - Prevent using exact same database schema/buckets/index for multiple tenants - update junit test
RED-5504 - Prevent using exact same database schema/buckets/index for multiple tenants - add junit test
RED-5504 - Prevent using exact same database schema/buckets/index for multiple tenants - add unique constraints to tenants table
* Changed the update to the DownloadStatusEntity to use the entity object instead of using a query on JPA-repo. This prevents values from the object being incorrectly inserted otherwise.
* Extended the DownloadPreparationTest to check the resulting download state and file size.