ADOT version: availability of OpenTelemetryCollector opentelemetry.io/v1

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?
ADOT deploys the OpenTelemetry Operator to EKS. However, it ships with very old CRDs. I only have v1alpha1 version of the OpenTelemetryCollector in my cluster.

This is suboptimal because at that version, the configuration is a multiline string. In subsequent versions the `config` key is part of the CR schema. We need to use at least v1beta1 but preferably v1 so that we can validate our collectors against the official schema **which should include the `config` key**.

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We validate our YAML against official schemas using CUE, Kubeconfirm etc. The v1alpha1 version of the collector defines the configuration as a schemaless string. We cannot validate the string against v1alpha1.

**Are you currently working around this issue?**
How are you currently solving this problem?
Trial and error in the `dev` environment.

**Additional context**
Anything else we should know?
Official Helm chart already ships with v1:
https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-operator/conf/crds/crd-opentelemetrycollector.yaml#L2

Start by comparing the CRD at the official Helm chart path `charts/opentelemetry-operator/conf/crds/crd-opentelemetrycollector.yaml` with the CRDs shipped by ADOT on EKS. Confirm which OpenTelemetryCollector versions and schema fields are available in the deployed operator, then verify that the v1 schema exposes `config` and supports validation against collector manifests.

Written by the indexing model from the issue text.