feat(controller): Allow for a configurable listen_host in network.yaml

[JTCunning]

Company or project name

N/A

Use case

Some kubernetes clusters operate in ipv4-only, ipv6-only, and dual-stack.

Describe the solution you'd like

Allowing for a configurable listen_host would enable users to conform to their networking restrictions.

Describe alternatives you've considered

We can either have a default with an override of the values supplied ie listen_host:[::, 0.0.0.0], or some sort of network_mode:ipv4-only/ipv6-only/dual-stack. Whatever makes the most sense, I'd lean towards the first.

Additional context

This arrived to us via customer feedback internally.

[GrigoryPervakov]

The default config is expected to work in all environments listen_try should help in case one of the entries is not available or both are available, and one is failing to bind because of the second. In case nothing succeeded, the liveness probe will fail, and Pod will be restarted by the controller.
As the default config has two entries, overrides become a bit trickier, but still possible

apiVersion: clickhouse.com/v1alpha1
kind: ClickHouseCluster
metadata:
  name: sample
spec:
...
  settings:
    extraConfig:
      listen_host:
        - "0.0.0.0"
        - '@remove': '1'