Multi tenancy support for the secureCodeBox API

[J12934]

This Pull Requests add Multi Tenancy support to the API of the secureCodeBox.

This allows Users to restrict access to ability to see and work on securityTests. This enables Users to scan services located in isolated networks, by restricting the access to Scans to the technical users of the scanner services inside these networks. By restricting the access to the securityTest to the isolated worker it is ensured that no other worker outside this network can "steal" this job.

The easiest way to configure multi tenancy is to create multiple camunda tenants and assign the technical users of the works to the corresponding tenant. To control to which tenant a securityTest should belong you can set the tenant attribute on the securityTest model, when starting a process. Note: You need to be a member of the tenant to start a process as part of the tenant. When the tenant attribute is set to null or is not set at all the process will be started without a tenant.

Open Todos:

• Add Documentation on how Multi Tenancy works and how to use it
• Find & Document a way to prevent tenant works to lock jobs without a tenant. (This should already be possible to do, by setting up the authentication correctly)

[J12934]

Due to the enforcement of Camunda permissions the ProcessDefinition READ permission is now mandatory for a user to have to successfully submit a job result. The other two (READ_INSTANCE and UPDATE_INSTANCE) were added as a precaution.

Note: This is a potential breaking change for users not using the scanner group provided by default for their scanner user permissions.
The permissions of the default scanner group will get updated by default, all others will have to manually expand their scanner groups to match these permissions.

[J12934]

Was able to solve "the tenant workers are getting non tenant specific work" by expanding out lock job controller. Workers with a tenant will only work on jobs belonging to their tenant while jobs without a tenant will only get handled by workers without a tenant.

So no default tenant required.