feat: support mountMode configuration to skip checking mount ready

[Syspretor]

As a premise, this PR clarifies a concept that has always existed in Fluid:
"MountMode". Historically, the processes responsible for executing the fuse mount actions have existed in two patterns: mountPod and sidecar.
The mountPod is initiated before the pod starts, performing the corresponding mount actions. Meanwhile, the NodePublishVolume interface of the Fluid CSI plugin implements a check_mount script to verify whether the mountPod has completed its mounting. However, in certain runtime scenarios where dataset.spec.mounts may initially be empty (such as thinRuntime or vineyard), there are no initial mount points, causing the check_mount validation of the NodePublishVolume interface to fail. This results in the inability to start pods using mountPod as the mountMode.

To address this issue, this PR defines the annotation fluid.io/skip-check-mount-ready-target in the runtime, with possible values as follows:

"": Skip none,
"All": Skill all mount mode to check mount ready,
"MountPodOnly": for only mountPod to skip check mount ready,
"SidecarOnly": for only sidecar to skip check mount ready,

This annotation will be processed by the runtime engine and transmitted as PV volume attributes to the CSI plugin. In the NodePublishVolume interface logic of the CSI plugin, it will check the mount readiness only when this annotation's value is either "MountPodOnly" or "All".

For example, we can declare a runtime that bypasses the CSI plugin's mount readiness check for the mountPod during the app pod startup process.

apiVersion: data.fluid.io/v1alpha1
kind: ThinRuntime
metadata:
  name: demo
  annotations:
    fluid.io/skip-check-mount-ready-target: "MountPod"
spec:
  profileName: demo

[cheyang]

fluid.io/check-fuse-mount-ready-pattern

I suggest the key should be skip-check-mount-ready-target， and default value is "".

[cheyang]

@Syspretor Please fix the conflict file. Thanks.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
10.1% Duplication on New Code

See analysis details on SonarCloud

[cheyang]

/lgtm
/approve

[fluid-e2e-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cheyang

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

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