refactor(restart demo setup): detect restart based on partner and skip demo setup

[tom-rm-meyer-ISST]

Description

solves #1063

Check functionality as follows (best with two terminals):

• Terminal 1: cd local && ./deploy.sh -c
• Termincal 2: docker compose logs puris-backend-customer puris-backend-supplier -f (as soon as deployment has been successfull)

Do per service (puris-backend-customer and puris-backend-supplier) in Terminal 1 and check in Terminal 2:

# if container has been rebuilt
docker compose up -d puris-backend-customer

# if container has not been rebuilt
docker compose logs puris-backend-customer -f

Notes: Solved it in two commits. I first did checks per entity which is kind of messy for this setup. In commit 2 I just detected the setup as done and skip the rest of the setup.

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files (TRG 7.02
• Documentation Notice are present on all affected files (TRG 7.07)
• If helm chart has been changed, the chart version has been bumped to either next major, minor or patch level (compared to released chart).
• Changelog updated (changelog.md) with PR reference and brief summary.
• Frontend version bumped, if needed (frontend/package.json, frontend/package-lock.json)
• Backend version bumped, if needed (backend/pom.xml)
• Open API specification updated, if controllers have been changed (use python script scripts/generate_openapi_yaml.py with running customer backend)

[ReneSchroederLJ]

LGTM. Thank you for the quick fix.