Implement OpenMCP bootstrapper with the usage of OCM K8S Toolkit

[reshnm]

Understand the Task

Implement the OpenMCP bootstrapper with the usage of the OCM K8S Toolkit. This will be used in the future to replace the initial bootstrapper version implemented by #45

Any further valuable resources.

No response

What is required to accept the Task as done.

Done Criteria

• ...
• Code has been reviewed by other team members
• Internal technical Documentation created/updated
• New / changed code is documented
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated
• Enduser Documentation updated (if applicable)
• Successful demonstration in Review

[In-Ko]

We discussed in the refinement that we have to dig a bit deeper into the current state of the OCM K8s Toolkit, and whether it can already provide the functionality we require for our OCM-based automated deployments / updates of MCP Landscapes.

[reshnm]

Ideas for the next steps:

Currently there is a apeiro-showroom that is being deployed according to this openmcp/apierora-showroom Github repository

1. Gain acceess and permissions to the openmcp/apierora-showroom repository
2. Gain access to the ApeiroRA Showroom. Please contact Aaron Schweig (I547291) aaron.schweig@sap.com to gain access
3. Gain access to the ApeiroRA Showroom, mcp and mcps Gardener projects. Please contact Robert or me to gain access

Currently in the apeiro showroom we are creating the Kubernetes manifests directly, with hard coded OCI image references

https://github.tools.sap/openmcp/apeirora-showroom/blob/main/1-openmcp-operator/deployment.yaml#L27 or
https://github.tools.sap/openmcp/apeirora-showroom/blob/main/3-cluster-provider-gardener/cluster-provider-gardener.yaml#L6

The idea is to create the manifests no longer directly, but use the openmcp-project/openmcp root component to create a subscription with the ocm-k8s-toolkit.
Together with the Kro the Kubernetes manifests that are currently created manually can be created by Kro to use the OCI image references provided by the ocm-k8s-toolkit.

There is also an example created by @sk31337 https://github.com/platform-mesh/httpbin-operator/tree/main/ocm that could be used to see how the interaction with the ocm-k8s-toolkit and Krow works.

[moelsayed]

I was a bit stuck trying to figure out how to access nested competent references in the ocm component version. But I managed to resolve that. I am currently working on trying to recreate the apierora showroom installation using the the k8s tool kit.

[moelsayed]

The initial implementation is in this PR. However, it's not sufficiently stable for production deployment.