feat: init data at back-end startup

Proposed Changes

This PR adds an config option to create mock data at startup. This feature is only available when using the development build tag.

It adds:

• A DAC A with the user alice as admin.
• A policy P for the DAC A.
• A submission that uses the policy P.

For now the identity of Alice is hard-coded and uses UUID and names similar to what is defined in our local dev Keycloak instance. If the Keycloak config changes (e.g., the UUID of alice changes), it will break.

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