Prevent users from setting 0.0.0.0 on any advertised_* address setting

[hcoyote]

See following for background redpanda-data/redpanda#12395

We have users continuing to trip up over the difference between kafka_api (the listener configuration) and advertised_kafka_api. We should proactively/fast fail an ansible run if the user attempts to set this because it's an incorrect configuration.

advertised_rpc_api and advertised_pandaproxy_api are also the other ones I'm aware of that need this sort of check, but we should verify there aren't others.

We probably also need to double check deployment-automation and verify we're not setting 0.0.0.0 in any advertised_* address examples.

@deniscoady would like this to get some higher priority if possible.