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

### 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](https://github.com/ClickHouse/clickhouse-operator/blob/main/internal/controller/clickhouse/templates/network.yaml.tmpl#L1-L3) 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.

Start with internal/controller/clickhouse/templates/network.yaml.tmpl and trace how network settings are exposed through the operator configuration. Compare existing configurable settings before deciding how a default and user override should be represented; done means users can select IPv4-only, IPv6-only, or dual-stack listening without breaking the default behavior.

Written by the indexing model from the issue text.