Create new dev version once PR is merged on main

[maximiliantech]

Understand the problem

I, as a developer, I would love to have dev be automatically in sync with our latest approved & merged changes.

Context

Specifically this would mean that whenever we merge a PR in one of our controller/operator repositories, we would trigger a pipeline to build new image(s) and apply any new manifests directly on dev.

Proposal Acceptance Criteria

• Every repository (mcp-operator, control-plane-operator, service-provider-xyz, etc.) should have the same mechanism to have a dev tag automatically created/updated with new changes on main.
• The dev environment is auto-updated with all latest dev-versions of all components.

How much traction does this feature have?

No response

[reshnm]

We should wait with this taks until we are able to spin up new OpenMCP landscapes with kind clusters.

[In-Ko]

Is on hold until we have the GitOpsify and Bootstrapper tasks done.

[In-Ko]

Removed parent issue, this can be handled independently.