fix: truncate monitoringdashboard CRD to fit into cc operator check

[yuwenma]

I tried the new CRD size in the operator and it passes the TestConfigConnectorE2E check.

related to #2217

Capture some solutions to the root cause:

1. Switch the cc operator's default applier to use server-side-apply. This requires upstream change to k-d-p feat: Enable server-side-apply on direct applier kubernetes-sigs/kubebuilder-declarative-pattern#399
2. Switch the cc operator to use the ApplysetApplier (use ssa already). This requires not setting the metadata.managedFields. But the DCL/TF based controllers already have many handlings around managedFields. So this may not be a good option.
3. Turn on the operator check in presubmit to capture this issue earlier.

[justinsb]

I was imagining we just remove all the descriptions with a transformation here:

k8s-config-connector/dev/tasks/generate-crds

Line 51 in 8331376

go run ./scripts/crd-tools reflow-descriptions --dir apis/config/crd/

, but I do agree that a lot of the information here is superfluous.

/approve
/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb

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

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

[justinsb]

(We can always revert this PR and try the other approach in 1.121)