chore: Switch liveness probe to tcp socket instead of httpGet

[sbernauer]

Description

In SUP-159 a customer wanted to enable security for the Namenode HTTP API.
This resulted in /dfshealth.html returning a 401 instead of a 200 - thus failing the liveness probe.

This PR allows customers to configOverride security for the HTTP APIs (hopefully until we support them natively)

We intentionally did not write a curl script that checks for 200 or 401 but just went with the TCP port.

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

# Author - [x] Changes are OpenShift compatible - [x] CRD changes approved - [x] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide). - [x] Helm chart can be installed and deployed operator works - [x] Integration tests passed (for non trivial changes) - [x] Changes need to be "offline" compatible 

# Reviewer - [x] Code contains useful comments - [x] Changelog updated - [x] Cargo.toml only contains references to git tags (not specific commits or branches) 

# Acceptance - [ ] Feature Tracker has been updated - [ ] Proper release label has been added - [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated 

[siegfriedweber]

LGTM

[sbernauer]

Thanks for the review!