feat: support pause and resume reconciliation of a cluster

[yipeng1030]

support cluster pause and resume

• Fixes [Features] Support Pause and Resume Reconcilation of a Cluster #6969

• Pause Cluster, Component, and InstanSet
  Annotate the cluster, cascade pause Components (by annotating) and InstanceSets (reuse the Paused field), after pausing, the three controllers will only handle delete operations.

• Pause Reconfigure and Configuration
  Asynchronous methods are not paused currently. (configconstraint.spec.reloadAction.*Trigger.sync = false)
  For synchronous reconfiguration operations, sending ops and modifying config are performed by the configuration operator rendering the configmap, and the changes to the configmap are implemented in the engine via Reconfigure_controller.go, thus the Configuration and Reconfigure controllers need to be paused.
  When the cluster resumes, modifying the corresponding configmap and configuration annotations will trigger a round of configuration tuning, and changes made during the pause will be applied.

• Pause Backup
  The backup operation aims to record the true status of the cluster, and after restoration from the backup, the cluster should serve exactly the same as before. The Spec of a paused cluster is different from its real status, and there is basically no way to fetch that information, thus Kubeblocks do not support backing up a paused cluster.

pause a cluster：
kubectl annotate cluster CLUSTER_NAME controller.kubeblocks.io/controller-paused="true"
resume a cluster：
kubectl annotate cluster CLUSTER_NAME controller.kubeblocks.io/controller-paused-

[CLAassistant]

All committers have signed the CLA.

[leon-inf]

hasPaused is calculated based on component objects, so it should set the dependencies for components to those CM objects explicitly.

[codecov]

Codecov Report

Attention: Patch coverage is 87.32394% with 18 lines in your changes missing coverage. Please review.

Project coverage is 61.38%. Comparing base (0ceeaa6) to head (cef893c).
Report is 3 commits behind head on main.

Files	Patch %	Lines
...ers/apps/configuration/configuration_controller.go	0.00%	3 Missing and 1 partial ⚠️
...llers/apps/configuration/reconfigure_controller.go	0.00%	3 Missing and 1 partial ⚠️
pkg/controller/model/transform_utils.go	0.00%	4 Missing ⚠️
controllers/apps/transform_utils.go	94.23%	2 Missing and 1 partial ⚠️
controllers/apps/transformer_cluster_pause.go	91.17%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7435      +/-   ##
==========================================
- Coverage   64.92%   61.38%   -3.54%     
==========================================
  Files         345      437      +92     
  Lines       42942    52098    +9156     
==========================================
+ Hits        27879    31982    +4103     
- Misses      12619    17472    +4853     
- Partials     2444     2644     +200     

Flag	Coverage Δ
unittests	61.38% <87.32%> (-3.54%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[yipeng1030]

ready for review

[Y-Rookie]

Should the pause and resume operations be executed before all transformers? According to your design, can a cluster that is being deleted be paused?

[yipeng1030]

Deletion has a higher priority than pause in my design, which is refer to the design of rollout pause of the k8s deployment.