Key cloak update

[MarvinFischer]

Description of changes

Updates the Keycloak version for local development and updates the Theme.

The theme is now more nested and reuse components. Adds margin classes. uses scss as preprocessor instead of pure css. Uses mostly css variables for colors when possible. The colour scheme has changed slightly. It uses now the Material Color Scheme based on a primary seed color of the meitrex project.

Note: It contains changes of #137 because of the dev branch diff

It also adds another default keycloak GITS realm import file to support gamification group as user attribute and the corresponding scope/claim.

How has this been tested?

The password reset feature needs to be enabled in the realm. It also requires the setup of a SMTP Server to send the email.

• automated unit test
• automated integration test
• automated acceptance test
• manual, exploratory test

In case of manual test, please document the test well including a set of user instructions and prerequisites. Each including an action, it's result, and where appropriate a screenshot.

Checklist before requesting a review

• My code follows the coding guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My code fulfilles all acceptance criteria
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have made corresponding changes to the documentation
• I have added explanation of architectural decision and rationales to wiki/adr
• I have updated the changes in the ticket description

Checklist for reviewer

• The code works and does not throw errors
• The code is easy to understand and there are no confusing parts
• The code follows the coding guidelines of this project
• The code change accomplishes what it is supposed to do
• I cannot think of any use case in which the code does not behave as intended
• The added and existing tests reasonably cover the code change
• I cannot think of any test cases, input or edge cases that should be tested in addition
• Description of the change is included in the documentation