[BUG] upgrade kb 0.8.3 to 0.9.0 redis cluster secret account kbadmin AUTH failed

[JashBook]

Describe the bug

kbcli version
Kubernetes: v1.29.4-gke.1043002
KubeBlocks: 0.9.0-beta.32
kbcli: 0.9.0-beta.24

AUTH failed: WRONGPASS invalid username-password pair or user is disabled.

To Reproduce Steps to reproduce the behavior:

1. install kubeblocks 0.8
2. create redis cluster

kubectl get secret -n ns-zquwfv
NAME                                                  TYPE     DATA   AGE
redis-zquwfv-conn-credential                          Opaque   5      17h
redis-zquwfv-redis-account-kbadmin                    Opaque   2      17h
redis-zquwfv-redis-account-kbdataprotection           Opaque   2      17h
redis-zquwfv-redis-account-kbmonitoring               Opaque   2      17h
redis-zquwfv-redis-account-kbprobe                    Opaque   2      17h


kubectl get secret  -n ns-zquwfv redis-zquwfv-conn-credential  -ojsonpath='{.data.username}'|base64 -d
default                                                                                                                                                                                
kubectl get secret  -n ns-zquwfv redis-zquwfv-conn-credential  -ojsonpath='{.data.password}'|base64 -d
97fshlkr                                                                                                                                                                                

kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbadmin  -ojsonpath='{.data.username}'|base64 -d
kbadmin                                                                                                                                                                          
kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbadmin  -ojsonpath='{.data.password}'|base64 -d         
0je6349Odh                                                                                                                                                                         

kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbdataprotection  -ojsonpath='{.data.username}'|base64 -d     
kbdataprotection
kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbdataprotection  -ojsonpath='{.data.password}'|base64 -d 
6j476vzJy5

kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbmonitoring  -ojsonpath='{.data.username}'|base64 -d
kbmonitoring
kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbmonitoring  -ojsonpath='{.data.password}'|base64 -d
SK1z167pF5                                                                                                                                                             

kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbprobe  -ojsonpath='{.data.username}'|base64 -d
kbprobe                                                                                                                                                                               
kubectl get secret  -n ns-zquwfv redis-zquwfv-redis-account-kbprobe  -ojsonpath='{.data.password}'|base64 -d
S7YN6l592m

3. upgrade kubeblocks to 0.9.0

kbcli cluster connect  -n ns-zquwfv redis-zquwfv --as-user default 
Password: Connect to instance redis-zquwfv-redis-1: out of redis-zquwfv-redis-1(primary), redis-zquwfv-redis-0(secondary)
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
127.0.0.1:6379> set test "1"
OK
127.0.0.1:6379> get test
"1"

4. See error

kbcli cluster connect  -n ns-zquwfv redis-zquwfv --as-user kbadmin
Password: Connect to instance redis-zquwfv-redis-1: out of redis-zquwfv-redis-1(primary), redis-zquwfv-redis-0(secondary)
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
AUTH failed: WRONGPASS invalid username-password pair or user is disabled.
127.0.0.1:6379> get test
(error) NOAUTH Authentication required.

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.

[Y-Rookie]

The accounts kbadmin, kbdataprotection, kbmonitoring, and kbprobe were not actually used in version 0.8, so they will not be provided by default in version 0.9. In version 0.9, the only default synchronization accounts will be default and kb-replicator.