E2E Test: Expand test coverage for HyperShift supported features

[hasueki]

Requesting Red Hat e2e testing to cover wider sets of common features that HyperShift supports to ensure stability in the subsequent releases. Some of these features may include, but not limited to:

• Bring your own PKI: https://github.com/openshift/hypershift/blob/80205d26e8f5605d82a5d9b2e2ca291263110129/api/v1beta1/hostedcluster_types.go#L20
• Disabling control plane profiling: https://github.com/openshift/hypershift/blob/80205d26e8f5605d82a5d9b2e2ca291263110129/api/v1beta1/hostedcluster_types.go#L110-L113
• OLM catalogs in guest cluster: https://github.com/openshift/hypershift/blob/80205d26e8f5605d82a5d9b2e2ca291263110129/api/v1beta1/hostedcluster_types.go#L338-L346
• Priority class overrides: https://github.com/openshift/hypershift/blob/8b33db92f0b694f33b4568395457a16ec877e49c/api/hypershift/v1beta1/hostedcluster_types.go#L41-L45
• ...

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/hypershift/issues/2455#issuecomment-1724639022): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[hasueki]

/remove-lifecycle rotten

[hasueki]

/reopen

[openshift-ci[bot]]

@hasueki: Reopened this issue.

In response to [this](https://github.com/openshift/hypershift/issues/2455#issuecomment-1816587447): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[brucejcong]

PRs: https://github.com/openshift/hypershift/pull/2989 https://github.com/openshift/release/pull/43084

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[hasueki]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale