PG based on Advanced StatefulSet

Enhancement request:
Can you consider optionally build PG statefulset based on OpenCruise?
https://openkruise.io/docs/user-manuals/advancedstatefulset/

Lets have the PG cluster
postgres-operator-6967dcf6c4-bcqjb 1/1 Running 2 38d
rob-dev-0 1/1 Running 5 38d
rob-dev-1 1/1 Running 3 38d
rob-dev-2 1/1 Running 2 38d
rob-dev-pooler-6767cc7474-pkxgn 1/1 Running 2 38d
rob-dev-pooler-6767cc7474-wkmpq 1/1 Running 2 36d
rob-dev-pooler-repl-7bfd87cd54-49bzr 1/1 Running 2 38d
rob-dev-pooler-repl-7bfd87cd54-mc9ld 1/1 Running 2 38d

{
"replica": [
"rob-dev-0"
],
"sync_standby": [
"rob-dev-1"
],
"leader": [
"rob-dev-2"
]
}

Now, we can have issue with PV used by replica rob-dev-0
From the Patroni point of view I can delete async replica and build a new one
using another PV.
But, because it's a Kubernetes statefuset, I can only delete rob-dev-2 or
rob-dev-2 and rob-dev-1. It's impossible to delete pod rob-dev-0
Using advanced statefulset, I can delete rob-dev-0 and build a new replica
rob-dev-4, for example
Regards, Hudec

The issue names no repository files or tests. Start by reading the OpenKruise AdvancedStatefulSet documentation and reviewing how the operator handles Kubernetes StatefulSets and Patroni replicas. Done means an optional configuration supports AdvancedStatefulSets and safely replaces the specified replica, with tests covering the behavior.