Fix default health probe binding address in helm chart

[adriananeci]

Description

There is a discrepancy between clusterRegistryClient.health.healthProbeBindAddress (defaults to 8081) and readiness/liveness probes port (defaults to 9091) default value

The health probe server is listening

2023-10-16T19:20:44Z	INFO	Starting server	{"kind": "health probe", "addr": "[::]:8081"}

while the liveness/readiness probes are checked on

  Warning  Unhealthy  6s    kubelet            Readiness probe failed: Get "http://172.16.18.218:9091/readyz": dial tcp 172.16.18.218:9091: connect: connection refused

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[JonnieDoe]

I do not know why the test fails. But the change is OK.

/lgtm