[BUG] DataLoad fails to launch when creating two types of Runtime CR sharing the same name

[TrafalgarZZZ]

What is your environment(Kubernetes version, Fluid version, etc.) 36e9634

Describe the bug DataLoad fails to launch after creating two types of Runtime CR sharing the same name. DataLoad's event shows that dataset-controller thinks the runtime is not ready.

Events:
  Type    Reason           Age                  From      Message
  ----    ------           ----                 ----      -------
  Normal  RuntimeNotReady  7s (x12 over 3m47s)  DataLoad  Bounded accelerate runtime not ready

By checking logs of the dataset-controller, it is like:

2023-11-28T11:17:06.346+0800    ERROR   dataloadctl.DataLoad    operations/base.go:53   Failed  {"DataLoad": "default/demo-dataset-load", "Command": ["jindo", "fs", "-report"], "FailedReason": "", "error": "pods \"demo-dataset-jindofs-master-0\" not found"}
github.com/fluid-cloudnative/fluid/pkg/ddc/jindofsx/operations.JindoFileUtils.exec.func1
        /go/src/github.com/fluid-cloudnative/fluid/pkg/ddc/jindofsx/operations/base.go:53

It uses JindoRuntime's health checker to decide whether the runtime is ready, but I'm running a JuiceFSRuntime sharing the same name with a JindoRuntime deleted a few moments ago.

What you expect to happen: DataLoad launches.

How to reproduce it

1. create a Dataset & JindoRuntime
2. create a DataLoad, and it will work well.
3. delete the Dataset & JindoRuntime
4. create a Dataset & JuiceFSRuntime with same name as the ones created before
5. create a DataLoad, DataLoad fails to launch

Additional Information