Provide alternative authorization with keycloak

[blcham]

Goal of the issue is to provide alternative authentication to the tool using keycloak module.

It should be done in a similar way as it was done for Record Manager, see kbss-cvut/record-manager#5, kbss-cvut/record-manager-ui#7. Also create docker-compose set up for fta-fmea-ui in folder deploy/keycloak-auth as can be seen in https://github.com/kbss-cvut/record-manager-ui/tree/main/deploy/keycloak-auth.

Note:

• there exist already some docker-compose set up here but it has more docker services defined than needed.
• you will need to switch database of fta-fmea-server to Graphdb (instead of RDF4j which was used until now). We did the same switch in Record Manager and we use now this service. Switch from RDF4J to Graphdb should not require any change of code.
• keycloak authorization module was developed by us here. When an application user is configured using keycloak UI, the module automatically replicates some data into GraphDB database.
• at the end we would like to add fta-fmea-ui and fta-fmea-server to set up https://github.com/kbss-cvut/record-manager-ui/blob/main/deploy/keycloak-auth/docker-compose.yml, thus it is good if you follow the same convention (or propose change also to the Record Manager)

A/C:

• it is possible to configure fta-fma-ui to use keycloak authorization or internal authorization
• unrelated part of the UI is hidden/disabled when keycloak authorization is enabled
• there is a docker-compose set up in deploy/keycloak-auth that can be used run the tool. It should include database, fta-fmea-server and fta-fmea-ui.
• graphdb is used in docker-compose set-up instead of rdf4j

[blcham]

@LaChope you can tackle frontend part of the ticket

[LaChope]

Re-opening as not completed

[LaChope]

Waiting for kbss-cvut/fta-fmea#87 to complete to continue this ticket.

[blcham]

Reopening as only UI was merged.

[LaChope]

#308 fixed logout issue and OIDC context.