Allow setting more than 1 core in the Cruise Control capacity confiuguration

A user has raised an issue regarding the CPU core capacity in the Cruise Control capacity configuration.

We currently use a cpuUtilization integer to set the CPU capacity but this is limited to a value of 100. This seems to map to Cruise Control thinking that the broker only has a maximum of 1 core.

Cruise Control capacity config allows you to set num.cores for whole cores but also seems to allow a percentage.

We currently limit the cpuUtilzation to 100. However, it is perfectly legitimate to assign multiple cores or fractions of cores to a broker pod. So it might make more sense to remove the 100 limit and allow the user to add 200 to indicate 2 cores (if this is indeed how it maps within Cruise Control). Alternatively we could add support for num.cores.