Update `NEEDS-RESTART` value when `redpanda.yaml` updates are detected

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

Users deploying with the helm chart are frequently surprised at the value of external advertised listeners and want to change this value. Today there is no way to do this without uninstalling and redeploying.

But this would require NEEDS-RESTART to take into account appropriate changes to redpanda.yaml (mainly redpanda.advertised_kafka_api).

What are the success criteria?

NEEDS-RESTART would get updated to true when a change to redpanda.advertised_kafka_api in redpanda.yaml is detected.

Why is solving this problem impactful?

The helm chart needs a way to determine if brokers need a restart, and one of the best ways to do this is by reading the value of NEEDS-RESTART in the output of rpk cluster config status.

Additional notes

Related helm issue: https://github.com/redpanda-data/helm-charts/issues/595

JIRA Link: CORE-1535

Start by tracing the redpanda.yaml configuration handling and the output of rpk cluster config status, focusing on changes to redpanda.advertised_kafka_api. Review the related Helm issue for deployment context. Done means NEEDS-RESTART becomes true when that configuration changes and the behavior is covered by the relevant existing tests.