[clusterobservability] reconcile managed resource updates and report rollout health

[jinja2]

Component(s)

cluster observability

Is your feature request related to a problem? Please describe.

ClusterObservability creates managed Collector and Instrumentation resources, but changes made after the initial reconciliation are not consistently propagated to them. This includes exporter config changes and new default images after an operator upgrade.

The resource can also remain Ready while a new Collector revision is failing to start, leaving users without a clear indication that their requested configuration did not roll out.

Describe the solution you'd like

• Keep managed Collector and Instrumentation resources in sync with the desired ClusterObservability configuration.
• Propagate updated operator image defaults to existing managed resources after an upgrade.
• Preserve metadata not owned by ClusterObservability and avoid updates when nothing has changed.
• Report rollout progress and failures for the current Collector revision, then return to Ready after recovery.
• Emit a Warning Event when reconciliation fails or a rollout first becomes unhealthy, without repeating it on every reconciliation.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}