fix: remove null creationTimestamp from CRDs to pass schema validation

[gazal-k]

creationTimestamp would be generated. Setting null does not seem to provide any benefit. It does fail schema validation using tools like https://github.com/yannh/kubeconform. So, remove the field.

[gazal-k]

Looks like the CRDs should be updated in https://github.com/open-telemetry/opentelemetry-operator/tree/main/bundle/community/manifests first 🤔 Shall create a PR for that.

[dmitryax]

@gazal-k, yes. If you have a chance, please submit a PR upsteam

[gazal-k]

https://github.com/open-telemetry/opentelemetry-operator/tree/main/bundle/ seems to be all generated. It seems to be using kustomize, it's not just creationTimestamp, but the generated CRDs and other resources seem to have status field too, which is puzzling 🤔

e.g:
https://github.com/open-telemetry/opentelemetry-operator/blob/1980f0877e5cff8e41ff3eafafe4c57133d7c899/bundle/community/manifests/opentelemetry.io_instrumentations.yaml#L1886-L1891

status:
  acceptedNames:
    kind: ""
    plural: ""
  conditions: null
  storedVersions: null