Avoid e2e to pass with faulty status

[swghosh]

Improves the verifyOperatorStatusCondition function to not allow bypassing status.Conditions when empty or has the required condition type(s) missing.

In #263, we managed to get the e2e pass with a faulty status update client that always kept the conditions array empty in the certmanager.operator/cluster resource.

• eg. job that Succeeded and it's corresponding operator log with panics

[swghosh]

/assign @lunarwhite
/cc @siddhibhor-56

[lunarwhite]

/test e2e-operator

[swghosh]

/label px-approved
/label docs-approved
Self-adding, no user facing changes.

[swghosh]

/hold
Need to update the condition count, and also verify Status.Generations is rightly populated.

[swghosh]

/remove-hold

we need the e2e with these changes to run successfully on #263,
helps us verify that .Status (with both .conditions and .generations) is/are updated correctly.

For context, we ran into an issue where server-side-apply (SSA) over .status.generations for the certmanager.operator object was broken in the CRD: https://redhat-internal.slack.com/archives/CE4L0F143/p1745930519786209.

[openshift-ci]

@swghosh: all tests passed!

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.

[lunarwhite]

/lgtm
/label qe-approved

Thanks for your work!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lunarwhite, swghosh

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 [swghosh]

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