[BUG]Failed to create minio cluster as serviceRefs of milvus cluster

[tianyue86]

Describe the bug
Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.32
kbcli: 1.0.0-beta.15

To Reproduce
Steps to reproduce the behavior:

1. Create minio cluster as serviceRefs of milvus cluster

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: miniom-itbjlz
  namespace: default
spec:
  terminationPolicy: WipeOut
  componentSpecs:
    - name: minio
      componentDef: minio-1.0.0-alpha.0
      replicas: 1
      env:
      - name: MINIO_BUCKETS
        value:
      disableExporter: true      
      resources:
        limits:
          cpu: 100m
          memory: 0.5Gi
        requests:
          cpu: 100m
          memory: 0.5Gi      
      volumeClaimTemplates:
        - name: data
          spec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi

2. Check cluster status

k get cluster -A
NAMESPACE   NAME                        CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
default     etcdm-itbjlz                                     WipeOut              Running    15m
default     miniom-itbjlz                                    WipeOut              Failed     9m43s
default     pulsarm-itbjlz              pulsar               WipeOut              Running    13m

3. check pod of minio

k get pod|grep minio
miniom-itbjlz-minio-0                      1/2     CrashLoopBackOff   6 (4m47s ago)    10m

k describe pod miniom-itbjlz-minio-0
Events:
  Type     Reason                  Age                    From                     Message
  ----     ------                  ----                   ----                     -------
  Normal   Scheduled               4m45s                  default-scheduler        Successfully assigned default/miniom-itbjlz-minio-0 to cn-zhangjiakou.10.0.0.139
  Normal   SuccessfulAttachVolume  4m44s                  attachdetach-controller  AttachVolume.Attach succeeded for volume "d-8vbit1xwtd9spxy1p7gg"
  Normal   AllocIPSucceed          4m32s                  terway-daemon            Alloc IP 10.0.0.84/24 took 37.480809ms
  Normal   Pulled                  4m32s                  kubelet                  Container image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/kubeblocks-tools:0.8.2" already present on machine
  Normal   Created                 4m32s                  kubelet                  Created container init
  Normal   Started                 4m32s                  kubelet                  Started container init
  Normal   Pulled                  4m31s                  kubelet                  Container image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/kubeblocks-tools:1.0.0-beta.32" already present on machine
  Normal   Created                 4m31s                  kubelet                  Created container init-kbagent
  Normal   Started                 4m31s                  kubelet                  Started container init-kbagent
  Normal   Created                 4m30s                  kubelet                  Created container kbagent-worker
  Normal   Pulled                  4m30s                  kubelet                  Container image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/minio:RELEASE.2024-06-29T01-20-47Z" already present on machine
  Normal   Started                 4m30s                  kubelet                  Started container kbagent-worker
  Normal   Pulled                  4m29s                  kubelet                  Container image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/minio:RELEASE.2024-06-29T01-20-47Z" already present on machine
  Normal   Created                 4m29s                  kubelet                  Created container kbagent
  Normal   Started                 4m29s                  kubelet                  Started container kbagent
  Warning  BackOff                 4m22s (x4 over 4m27s)  kubelet                  Back-off restarting failed container minio in pod miniom-itbjlz-minio-0_default(667fed07-7471-4000-864b-0ba768e7e0de)
  Normal   Pulled                  4m7s (x3 over 4m29s)   kubelet                  Container image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/minio:RELEASE.2024-06-29T01-20-47Z" already present on machine
  Normal   Created                 4m7s (x3 over 4m29s)   kubelet                  Created container minio
  Normal   Started                 4m6s (x3 over 4m29s)   kubelet                  Started container minio
  Normal   roleProbe               3m29s                  kbagent                  {"instance":"miniom-itbjlz-minio","probe":"roleProbe","code":0}

4. See error

the minio replicas history is 1
the minio server pool is  http://miniom-itbjlz-minio-{0...0}.miniom-itbjlz-minio-headless.default.svc.cluster.local/data
Starting minio server with command: /usr/bin/docker-entrypoint.sh minio server  http://miniom-itbjlz-minio-{0...0}.miniom-itbjlz-minio-headless.default.svc.cluster.local/data -S /etc/minio/certs/ --address :9000 --console-address :9001
ERROR Unable to prepare the list of endpoints: Incorrect number of endpoints provided [http://miniom-itbjlz-minio-{0...0}.miniom-itbjlz-minio-headless.default.svc.cluster.local/data]
      > Please provide correct combination of local/remote paths
      HINT:
        For more information, please refer to https://min.io/docs/minio/linux/operations/concepts/erasure-coding.html

Expected behaviorA clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[shanshanying]

Create at least 2 replicas for Minio.

[shanshanying]

@fengluodb PTAL, please add replicasLimit to minio and pulsar minio if missing.

[shanshanying]

• chore: minio add replicas limit kubeblocks-addons#1528