feat: cleanup docker mess and make keycloak work

Proposed Changes

• Explore token access.
• Cleanup docker compose file.
• Add working keycloak setup. A config file is loaded witha realm data-custodian on startup. Save the file with just save-keycloak if you make changes.
• Only config.docker.dist.yml files for now, nothing else
• Only secrets.dist.yml for now, all secrets are set over env. vars in docker-compose.
• Only minimal amount of env. vars.
• Improve Readme and add just file.

@martinfontanet, @LuanaMartelli : @LuanaMartelli helped me in fixing the docker setup today. Keycloak works, healthchecks on rabbitmq, mongodb etc. Docker compose now works nicely, also with the fixed IP addresses on gateway and keycloak to let the OIDC magic work.

@martinfontanet: Could you still review the gateway changes. I fixed some small missalignment with the login page url, thats all.

! This is clean up is of utter importantance: Docker compose must work and I want that everybody is able to start this beast without any strange config files and copy pasta and gimmick stuff. It should be KISS. Ok, the keycloak instance is a bit the problem. But we can store a realm and settings int the repo with some default users etc. See realm-data-custodian.json and make keycloak work.

Types of Changes

What types of changes does your code introduce? Put an x in the boxes that apply

• A bug fix (non-breaking change which fixes an issue).
• A new feature (non-breaking change which adds functionality).
• A breaking change (fix or feature that would cause existing functionality to not work as expected).
• A non-productive update (documentation, tooling, etc. if none of the other choices apply).

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING guidelines.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation (if appropriate).

CI Attributes

build:
  lazy: true # Use this experimentally only! (this uses change detection)

images:
#   push: true # Push the images to a temporary space to test it.
#   useReleaseTag: true  # Use a release version tag.

Further Comments