Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(operator): apply configured health probe endpoint names

The config API, the base manifests, and the Helm chart all expose
readinessEndpointName and livenessEndpointName, but the manager never received
them, so the probes stayed on controller-runtime's own /readyz and /healthz. A
deployment that renamed an endpoint and pointed its probe at the new path got a
404 back and a container that never turned ready.

Every place these names are configured spells them without a leading slash,
while controller-runtime registers them as http.ServeMux patterns, which panic
on a pattern that has none. They are rooted on the way through so the shipped
defaults keep serving where the probes already look, and the startup log now
reports the paths that were registered rather than the two it assumed.

Signed-off-by: rjgoyln <pt40419@gmail.com>