The Cruise Control Capacity configuration generator seems to completely ignore the resource request today. That seems to result in weird situations. For example:

1. When the request is set to 5 CPU and the limit is set to 10 CPU, Strimzi decides to ignore both and sets the CPU capacity to 1.0 which seems to be clearly wrong. While I think preferring the limit might be questionable and subjective, setting the CPU to 1.0 seems clearly wrong since it is well below both the limit and request.

1. When the request is set to 5 CPU and the limit is not set, Strimzi decides to ignore the request and sets the CPU capacity to 1.0 which seems to be clearly wrong. While the current code seems to prefer a limit instead of a request and in this case, the limit is unknown ... setting 1.0 as the capacity seems clearly wrong since the request of 5 CPUs is clearly much higher and these CPUs will be always available.

We should update the logic to either take the request configuration properly into account or at least not misconfigure it by setting the CPU capacity to 1.0 when we cannot decide.

Created by Strimzi#8576