Feature Request: Bump apiVersion of opentelemetry collector

[viccuad]

From Martin:

Here we use apiVersion: opentelemetry.io/v1alpha1 but in 0.102.0 there is v1beta1. The deployment seems to work well but Fleet seems to have a problem to compare properly. Is there a chance to change this to v1beta1?

Acceptance criteria

• Bump mentioned apiVersion in our opentelemetry collector instance.
• Make sure spec.Config matches the new schema for v1beta1 version of the spec.
• Perform opentelemetry tests and verify everything is fine.
• Perform upgrade test on a deployment with opentelemetry and verify that everything is fine.
• Make sure that the pinned versions of the charts for the telemetetry stack in docs.kubewarden.io match the minimum versions needed for this feature.

[flavio]

I would tackle this change together with the bumps of the otel crates

[viccuad]

Reopening; the change was reverted, and it seems the template for the CR needs adjustment as there are spec changes in spec.config besides the apiVersion bump: (edited acceptance criteria)

Error: 1 error occurred:
        * admission webhook "mopentelemetrycollectorbeta.kb.io" denied the request: json: cannot unmarshal string into Go struct field OpenTelemetryCollectorSpec.spec.config of type v1beta1.Config

[viccuad]

IMHO we need to wait for this feature request, as the minimum dependency versions we list at https://docs.kubewarden.io/reference/dependency-matrix will of course not support this change.

Given that the current latest chart, opentelemetry-operator-0.64.0, is still accepting v1alpha1, and provides the apiVersion migration, I think it's fine to wait.