add manage-cert-rotation: yes label to cs-ca-certificate CR

[qpdpQ]

What this PR does / why we need it:
add manage-cert-rotation: yes label to cs-ca-certificate CR
update operator code to ignore reconciling renewBefore field

Which issue(s) this PR fixes:
Fixes # https://github.ibm.com/IBMPrivateCloud/roadmap/issues/66198

Special notes for your reviewer:

How the test is done?
we could use this image to test quay.io/yuchen_li1/common-service-operator-amd64:dev

1. update the RenewBefore time in cs-ca-certificate
2. delete cs-operator pod to trigger a new reconcile
3. updated renewBefore time shouldn't get reverted after a new reconcile

How to backport this PR to other branch:

1. Add label to this PR with the target branch name backport <branch-name>
2. The PR will be automatically created in the target branch after merging this PR
3. If this PR is already merged, you can still add the label with the target branch name backport <branch-name> and leave a comment /backport to trigger the backport action

[ibm-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qpdpQ

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

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

[qpdpQ]

test logs:

I0326 18:17:16.848615 1 init.go:1410] Deploying Cert Manager CRs
I0326 18:17:21.455972 1 request.go:601] Waited for 1.046490674s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/monitoring.coreos.com/v1beta1?timeout=32s
I0326 18:17:27.509430 1 init.go:1443] Checking Cert Manager Certs and Issuers deployment
I0326 18:17:27.727635 1 init.go:473] create or update certificate
I0326 18:17:27.731036 1 init.go:490] ignore renewBefore
I0326 18:17:27.731059 1 init.go:491] renewBefore in cluster: 6000h0m0s
I0326 18:17:27.731066 1 init.go:492] renewBefore in code: 5840h0m0s

[Daniel-Fan]

Hi @qpdpQ

I am thinking that CS operator will never "update" a certificate resource given this resource does not have .metadata.annotations.version defined.

Can you have a test on CS operator without above particular Certificate Kind handling logic, and see if CS operator will update the certificate? Thank you!

[qpdpQ]

add a new field disableManageCertRotation in commonservice.spec it is set to false by default