Cluster chart 0.8.1 console uses non-existent `cluster-superuser` secret

With the cloudnative-pg operator chart v0.29.0 and the cluster chart v0.8.1, enabling the console gives me a container that can't start because there's no `cluster-superuser` secret available. The `cluster-api` secret does contain the keys though, so patching these fields with kustomize so they use the `cluster-api` secret instead:
```yaml
- name: DB_SUPERUSER_HOST
valueFrom:
secretKeyRef:
name: {{ include "cluster.fullname" $ }}-superuser
key: host
- name: DB_SUPERUSER_PORT
valueFrom:
secretKeyRef:
name: {{ include "cluster.fullname" $ }}-superuser
key: port
- name: DB_SUPERUSER_USER
valueFrom:
secretKeyRef:
name: {{ include "cluster.fullname" $ }}-superuser
key: user
- name: DB_SUPERUSER_PASSWORD
valueFrom:
secretKeyRef:
name: {{ include "cluster.fullname" $ }}-superuser
key: password
```
makes the console start.

Inspect the cluster chart template that configures the console container and compare its superuser secret references with the available cluster-api secret. Render or deploy the chart with the console enabled, then verify the container starts and its database connection settings resolve successfully.

Written by the indexing model from the issue text.