Update TLS endpoints to use OpenShift API server configuration

[rhmdnd]

We have a results server that exposes a TLS 1.2 endpoint. This is fine today, but pulling this from a more authoritative source, like the OpenShift API server is better because then a user can configure it in a single place and have the change propagate to the Compliance Operator automatically.

This commit updates the operator to use the OpenShift API server TLS configuration, instead of hard-coding it to TLS 1.2. If the operator encounters issues fetching the API server configuration, it defaults back to TLS 1.2.

Assisted-By: Claude

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhmdnd

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~~ [rhmdnd]

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

[github-actions[bot]]

:robot: To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:1000-1ae198189003d84371baa5c07f39fd465ec7ae99

[openshift-ci[bot]]

@rhmdnd: 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/e2e-aws-serial	1ae198189003d84371baa5c07f39fd465ec7ae99	link	true	/test e2e-aws-serial

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.

[rhmdnd]

We'll need a way to test this in conjunction with the API server so that we know it's working as expected.