podAntiAffinity disallows more than one cluster

Summary

we've just deployed a new cluster, the stateful podAntiAffinity rules seem to have changed so we now cannot deploy more than one DB.

Current Behaviour

        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchExpressions:
              - key: app
                operator: In
                values:
                - StackGresCluster
              - key: stackgres.io/cluster
                operator: In
                values:
                - "true"
            topologyKey: kubernetes.io/hostname

Steps to reproduce

Deploy a cluster with the current version of stackgres from helm (1.2.1).

Expected Behaviour

        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchExpressions:
              - key: app
                operator: In
                values:
                - StackGresCluster
              - key: stackgres.io/cluster-name
                operator: In
                values:
                - "<CLUSTER NAME>"
            topologyKey: kubernetes.io/hostname

Environment

• StackGres version: 1.2.1

• Kubernetes version: v1.25.2