Development: Add postgres docker compose setup

[4ludwig4]

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

As we want to move towards Postgres, we already implemented a Docker container. We also add support for Docker Compose Setups to enable developers to try Postgres with Artemis quickly.

Description

We streamlined the official naming of PostgreSQL to Postgres as this informal naming is used in the rest of the project, apparently.
We streamlined the common cypress configurations into a common .env file.
We added Artemis Docker Compose Setups for Postgres and updated the Docs.
Therefore we introduced a new Docker Compose section in the administrator section of the Docs.

Steps for Testing

Artemis Postgres Prod Setup

1. change the permissions in your repository according to the administrator documentation for the prod setup
2. run the Artemis Postgres Prod Setup: docker compose -f docker/artemis-prod-postgres.yml up
3. check Artemis
4. shutdown Artemis Postgres Prod Setup: docker compose -f docker/artemis-prod-postgres.yml down and optionally delete the contents of ./docker/.docker-data/artemis-postgres-data

Artemis Postgres Dev Setup

1. run the Artemis Postgres Dev Setup: docker compose -f docker/artemis-dev-postgres.yml up
2. check Artemis
3. shutdown and delete the volumes of Artemis Postgres Prod Setup: docker compose -f docker/artemis-dev-postgres.yml down -v

Check that the other Docker Compose setups you are using still work.

Review Progress

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

[TheZoker]

Changes LGTM 👍

[jakubriegel]

Code looks good 👍🏻
Both local and dev set up work on my machine 👍🏻

I think merge should be synchronised with #6443. Artemis was much slower than on MySQL for me, but that my be connected to arm vs x64 container.

[4ludwig4]

I think merge should be synchronised with #6443.

@jakubriegel What do you mean with "synchronized"? There shouldn't be any conflicts between the two PRs.

[jakubriegel]

I think merge should be synchronised with #6443.

@jakubriegel What do you mean with "synchronized"? There shouldn't be any conflicts between the two PRs.

Just to make sure that this change also supports arm. It is does, then nothing more to be done here

[4ludwig4]

@jakubriegel @TheZoker can you please re-approve if my commit to fix the merge conflicts looks good?

[4ludwig4]

Fixed the merge conflicts again.

[Hialus]

Went through the code again and it still looks good to me 🚀

[4ludwig4]

Fixed the merge conflicts again.