feat: add deployment environments

[JSPRH]

Description

Add the deployment infrastructure for next and prod environments.

Next: next.kordis-leitstelle.de | api.next.kordis-leitstelle.de
Prod: app.kordis-leitstelle.de | api.kordis-leitstelle.de

Todo:

• Note deployment flow possibilities
• Generate deployment credentials for pipeline
• Collect commands for deployment
• Setup deployment pipelines
• Write ADR for infrastructure setup

Deployment options

1. Via Tags

• Everything happens in the kordis-leitstelle/kordis repo
• Every push to main triggers a pipeline setting the image on the next overlay and deploys that
• Tagging is done by hand and triggers a pipeline tagging the current image with the version tag and setting it on the prod overlay and deploys that
• Downside: We don't have the tags of containers in version control however this is not really an issue as the tag is either the commit sha or the version tag

2. Via Tags but prod deployments are PRs

• For next stage same as in option 1
• Deploying to production works via PR (or similar)
  • Within this PR, the tags of the container images are set to the version which will be created by the deployment
  • The PR pipeline, upon merging, tags the containers with the version tag and deploys overlay prod

3. Via kordis-leitstelle/infrastructure

• We move all kordis infrastructure over to the kordis-leitstelle/infrastructure repository, which then holds responsibility for deploying
• Every push to main triggers a pipeline in the infrastructure repo, creating a commit for setting the image tags in the overlay and deploys, same for production deployments via tags
• Upside: This repo remains more "clean" from operations and focuses on the software; we version control our infrastructure via GitOps

Deployment commands

Set container images: kustomize edit set image kordis-api=ghcr.io/kordis-leitstelle/kordis-api:8683454f374b5989ae30882db5b584152bab715a

Checklist:

• The title of this PR and the commit history is conform with
  the Conventional Commits specification.
• I have performed a self-review of my own code.
• My changes generate no new warnings, SonarCloud reports no Vulnerabilities, Bugs or Code Smells.
• I have added tests (unit and E2E if user-facing) that prove my fix is effective or that my feature works,
  Coverage > 80% and not less than the current coverage of the main branch.
• The PR branch is up-to-date with the base branch. In case you merged main into your feature branch, make sure you have run the latest NX migrations (nx migrate --run-migrations).

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[JSPRH]

Moved to kordis-leistelle/infrastructure Pull Request #10