redpanda: Allow for configurations to be stored and shared across nodes

[rkruze]

Currently, all configurations have to be set on a per-node basis. This makes settings configurations, like a license key or other cluster wide configurations difficult as it requires having to push a new config to every node. Ideally, cluster-wide configurations would be stored in redpanda itself. Our current configurations manager used in rpk can pull configurations from etcd, which might be very similar to using a compacted topic in redpanda. https://github.com/spf13/viper#remote-keyvalue-store-support

[rkruze]

It would also be great if users didn't have to specify a node_id when starting a new node. This should be something that should just be auto-assigned to new nodes as they join the cluster.

[dotnwat]

Assigning @jcsp I think this ticket is effectively an alias for centralized configuration.

[jcsp]

It would also be great if users didn't have to specify a node_id when starting a new node. This should be something that should just be auto-assigned to new nodes as they join the cluster.

Created this ticket for auto selecting node_id (#2793) -- it's more of a standalone change than something that overlaps with central config.

[jcsp]

Resolved in 22.1