[BUG]1.0 mongodb cluster is always in Creating status

[tianyue86]

Describe the env

Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.8
kbcli: 1.0.0-beta.3

To Reproduce
Steps to reproduce the behavior:

1. Create mongo cluster using this yaml

apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: mongo-bxkpkz
  namespace: default
spec:
  terminationPolicy: DoNotTerminate
  clusterDef: mongodb
  topology: replicaset
  componentSpecs:
    - name: mongodb
      serviceVersion: 5.0.28      
      replicas: 3
      serviceAccountName: kb-mongo-bxkpkz      
      resources:
        limits:
          cpu: 100m
          memory: 0.5Gi
        requests:
          cpu: 100m
          memory: 0.5Gi      
      volumeClaimTemplates:
        - name: data # ref clusterDefinition components.containers.volumeMounts.name
          spec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi

2. Check pod

mongo-bxkpkz-mongodb-0          2/2     Running   0          13m
mongo-bxkpkz-mongodb-1          2/2     Running   0          13m
mongo-bxkpkz-mongodb-2          2/2     Running   0          12m

3. cmp in Creating status

Events:
  Type    Reason                    Age    From                  Message
  ----    ------                    ----   ----                  -------
  Normal  Unknown                   5m54s  component-controller  the component phase is unknown
  Normal  ComponentPhaseTransition  5m54s  component-controller  component is Creating
  Normal  Unavailable               5m54s  component-controller  the component phase is Creating

4. check cluster details
   ===> The component status is not updated, which may be a problem of the controller

Expected behavior
A 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.

[tianyue86]

This problem fixed by updating addon.