Upstream issue: https://github.com/strimzi/strimzi-kafka-operator/issues/6265

In order to guarantee accurate rebalance proposal when using CPU goals on nodes with heterogeneous CPU resources you can set CPU requests equal to CPU limits in `Kafka.spec.kafka.resources`. That way, all CPU resources are reserved upfront and are always available. However, this sidelines CPU resources even when they are not being used. Following [1], we should look into either

(1) Creating a custom BrokerCapacityConfigResolver [2] to get CPU+NW information from nodes 

(2) Patching upstream CC metric reporter to detect CPU+ NW information from nodes

(3) User capacity overrides

Investigation doc here [3]

[1] https://github.com/strimzi/strimzi-kafka-operator/pull/5992#discussion_r774045642

[2] https://github.com/linkedin/cruise-control/wiki/Pluggable-Components#broker-capacity-config-resolver

[3] https://docs.google.com/document/d/194sTGo_kPM20MdkW0x9r535E9ro9Y8H7rCZ1D0XEn6M/edit