When replacing hardware, kafka brokers in the cluster retain their original broker-id to avoid shuffling around partitions.

However since we do not reuse FQDNs, the brokers may at times have misleading broker ids (ex. kafka-main2008.codfw.wmnet: id: 2003)

We should update roll-restart-reboot-brokers.py[0] to identify both the broker id and FQDN of the broker currently assigned.

See hieradata/common.yaml#791 [1] for the full host to broker.id mapping.

[0] - https://gerrit.wikimedia.org/r/plugins/gitiles/operations/cookbooks/+/refs/heads/master/cookbooks/sre/kafka/roll-restart-reboot-brokers.py
[1] - https://gerrit.wikimedia.org/g/operations/puppet/%2B/7eb871c12c16ad52d34620c7114ca6539434fd2b/hieradata/common.yaml