knative-operator sends otel data even though otel-collector might not be up and running

knative-operator will always send otel-collector information (namespace, svc name, port) regardless of the status of the k8s resources. We must ensure that the resource is up and running before sending this data. This does not only apply to otel-collector, but can apply to other k8s resources.

Locate where knative-operator assembles otel-collector namespace, service, and port data, then inspect how Kubernetes resource readiness is represented. Define the expected behavior when resources are unavailable and verify that it applies to otel-collector and other resources.

Written by the indexing model from the issue text.