Fix Dependabot CI Pipeline

The Branches that Dependabot creates dont succeed. According to the job logs, they cant authenticate to the registry where the images should be pushed. This seems to be related to dependabot requiring credentials to be allowed to push, which currently are not provided to dependabot to restrict malicious dependencies of reading the registry credentials on automatic updates by dependabot.

• https://docs.github.com/en/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configuring-access-to-private-registries-for-dependabot

We have several options now:

• Ignore publishes and just merge on success of build & test steps, leaving the pipeline as-is and always creating faulty pipelines
• Restrict docker push to non-dependabot authored branches only
• Use renovate instead of dependabot, although renovate will suffer the same problem when trying to push
• Use pnpm instead of npm when building images. pnpm by default ships with version 11 (current, stable) a minimumReleaseAge that only allows builds of an application that is at least 24hours old. (this can be configured to whatever is needed. specified in minutes). https://pnpm.io/settings#minimumreleaseage
• provide dependabot with credentials to push to the registry. -> Do we ever need to have an image available of a patch/minor/major release in a seperate image?

Start with the Dependabot-created branch job logs and the CI pipeline steps that build and push images to the registry. Determine which publishing behavior is intended for Dependabot branches, then verify that the selected approach lets build and test jobs complete without exposing registry credentials or leaving expected pipelines faulty.