rpk redpanda config bootstrap to bootstrap advertised addresses

[r-vasquez]

Who is this for and what problem do they have today?

Currently, rpk redpanda config bootstrap initializes the configuration to bootstrap a cluster, but it only initializes the kafka/rpc listeners and not their respective advertised addresses.

This is problematic now that #14600 introduced a default advertised_ address in the configuration file.

What are the success criteria?

When running rpk redpanda config bootstrap

1. A user should be able to override the default `advertised_{kafka,rpc}_address.
2. If no override is provided, rpk should follow the same logic as redpanda: use the listener address as the advertised address.
3. rpk should fail if the resulting configuration is an advertised address using 0.0.0.0.

Why is solving this problem impactful?

Currently, extra steps are required to start redpanda using the default configuration:

rpk redpanda config bootstrap

rpk redpanda set redpanda.advertised_kafka_api <advertised_address>
rpk redpanda set redpanda.advertised_rpc_api <advertised_address>

This can be avoided and handled properly with just rpk redpanda config bootstrap.

Additional notes

Original issue: #12395