[feature](dcr) add rolling restart capability

[catpineapple]

What problem does this PR solve?

• fe rolling restart capability
• be rolling restart capability

Principle：

restart capability triggers a restart by patching the template metadata of all the pods of resource with apache.doris.org/restartedAt annotation.

Directions：

1. Add corresponding annotations to dcr.metadata.annotations to rolling restart.
   a. apache.doris.be/restartedAt restart be
   b. apache.doris.fe/restartedAt restart fe
2. Try to ensure that the time is after the current time. The time in the past will be regarded as an invalid parameter and the restart will be rejected. The format can refer to this command: date +"%Y-%m-%dT%H:%M:%S%:z".

apiVersion: doris.selectdb.com/v1
kind: DorisCluster
metadata:
  labels:
    app.kubernetes.io/name: doriscluster
    app.kubernetes.io/instance: doriscluster-sample
    app.kubernetes.io/part-of: doris-operator
  name: doriscluster-sample
  namespace: doris
  annotations:
    apache.doris.be/restartedAt: "2024-11-21T14:35:56+08:00"
    apache.doris.fe/restartedAt: "2024-11-21T15:20:56+08:00"
spec:
  feSpec:
  ...

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[intelligentfu8]

LGTM