What problem does this PR solve?

This PR allows users to mount a shared persistent volume into different pods. This ability is handy for sharing plugins.
If you want to install the same plugin into different components' pods, and you don't want to install it many times for different pods. you can use this ability.
example as follows:

spec:
  sharedPersistentVolumeClaims:
  - mountPath: /mnt/xxx/xx
    persistentVolumeClaimName: share-pvc
    supportComponents:
    - fe
    - be

• mountPath is the absolute path in the container. mountPath also supports an environment variable ${DORIS_HOME} config in the prefix path.
  For FE, the ${DORIS_HOME} is /opt/apache-doris/fe.
  For BE, the ${DORIS_HOME} is /opt/apache-doris/be.
  this can be used to mount a shared pv into same relative path to ${DORIS_HOME}, because many plugins need to install the relative path of ${DORIS_HOME} to all fe, be.
• persistentVolumeClaimName is the persistentVolumeClaim's name that you should have created before deploying doris cluster. the pesistentVolumeClaim should have ReadWriteMany accessMode.
• supportCompoents specify what components need mount the shard pv. if the supportComponents is empty, it represents all component need mount the shard pv.

Issue Number: close #372

Related PR: #xxx

Problem Summary:

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