ACM-11757: refactor status update management to avoid flapping status

[thibaultmg]

This PR changes how the addon status reporting is managed, based on this specification.

It first implements a status package that enables atomic update of each component's status by adding two specific condition types in the addon conditions list: MetricsCollector and UwlMetricsCollector.
This package is used by the endpoint operator to set the UpdateSuccessful or UpdateFailed reasons (plus some others), and by the metrics collector to set the ForwardSuccessful or ForwardFailed reasons for each collector.

In order to avoid the flapping behavior described in the linked issue, it forbids some transitions such as UpdateFailed -> ForwardXxx. The idea is that to report a consistent status, the collector must first be in the state required by the endpoint operator.

These specific condition types are then aggregated by the status controller into the expected condition types by ACM (Available, Degraded and Progressing).

One edge case that is not handled here is if the collector pod stops after having set the reason to ForwardSuccessful. In such a case, we get an Available status while it is not working. We could add more logic, requiring the collector to do regular updates on its condition timestamp and the controller would monitor this. Let's keep it simple while nobody complains about it 😄

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[philipgough]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: philipgough, thibaultmg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [philipgough,thibaultmg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

New changes are detected. LGTM label has been removed.

[sonarqubecloud]

Quality Gate failed

Failed conditions
B Security Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[openshift-ci]

@thibaultmg: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/sonarcloud	9645628	link	false	/test sonarcloud

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.