[bitnami/postgresql-ha] Cloning huge data from primary node fails due to livenessProbe

[percenuage]

Description of the change

Update livenessProbe in order to check if process are in "data standby clone" step. If the synchronization from primary are longer than the livenessProbe fails, the replicas will restart in loop. It works for small data since it's fast but not with more than 20Go (I have 300 Go on primary on SSD and it has taken around 25 min to sync).

Maybe there is a special command from PG to check but I haven't found any.

Personal thanks to @exename (https://github.com/bitnami/charts/issues/4894#issuecomment-1616449097)

Benefits

Allows flexibility to add replicas during the run with existing data.

Applicable issues

• fixes #3556
• fixes #4894

Checklist

• [x] Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• [x] Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• [x] All commits signed off and in agreement of Developer Certificate of Origin (DCO)