feat(GSGGR-581): per-request permission management

[lanseg]

Purpose: per-request user ownership, make it possible for one operator to make a single request visible to another operator, even if the second operator is not an owner of the parent process.

Behavior:

1. Admin user sees all requests, no matter what users or groups are configured for the request or process
2. User can see or modify request if any of this applies:
   1. User or user's group is added to a Request
   2. User or user's group is added to a parent Process of this request
3. A request-owning User can modify request-owning users and groups.
4. After the user removes themselves from the request owners list, per-process ownership rules apply.

[maltaesousa]

That's a great addition, thanks!

[maltaesousa]

@lanseg I'm approving this but I didn't review the code, I've no experience in Java :(

Could you add the new tables to a SQL file, please? The project doesn't have migrations mechanism, we run sql files to existing databases when we upgrade and I think this new functionality will be merged later into asit :)
If you don't have time to do it, tell me and I can have a look at it.

[lanseg]

@lanseg I'm approving this but I didn't review the code, I've no experience in Java :(

Could you add the new tables to a SQL file, please? The project doesn't have migrations mechanism, we run sql files to existing databases when we upgrade and I think this new functionality will be merged later into asit :) If you don't have time to do it, tell me and I can have a look at it.

Added key migrations, similar to the exising ones.
For me tables and keys were created automatically, by spring/hibernate itself, so there should be no problem with migration.