[BUG] specifying user defined SA when creatiing cluster, the SA should be granted with certain ROLES to perform actions.

[shanshanying]

To Reproduce
Steps to reproduce the behavior:

1. create an SA, e.g. 'workload-identity-sa'
2. create a redis cluster with the sa

apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
  name: redis-replication-cluster
spec:
  clusterDefinitionRef: redis
  topology: replication
  terminationPolicy: Delete
  componentSpecs:
  - name: redis
    replicas: 2
    disableExporter: true
    serviceAccountName: "workload-identity-sa"
    resources:
      limits:
        cpu: '1'
        memory: 1Gi
      requests:
        cpu: '0.5'
        memory: 0.5Gi
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi
  - name: redis-sentinel
    serviceAccountName: "workload-identity-sa"
    replicas: 3
    resources:
      limits:
        cpu: '0.5'
        memory: 0.5Gi
      requests:
        cpu: '0.5'
        memory: 0.5Gi
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi

4. check SA and roles, e.g. can
   k auth can-i list pods --as=system:serviceaccount:default:workload-identity-sa -n default
   the answer is 'NO'. and the expected answer is 'YES', otherwise 'lorry' sidecart fails.