Fix unit tests following bug fix in CPUManager for map functions (2/2)
Fix unit tests following bug fix in CPUManager for map functions (2/2)

Now that the algorithm for balancing CPU distributions across NUMA nodes is
correct, this test actually behaves differently for the "packed" vs.
"distributed" allocation algorithms (as it should).

In the "packed" case we need to ensure that CPUs are allocated such that they
are packed onto cores. Since one CPU is already allocated from a core on NUMA
node 0, we want the next CPU to be its hyperthreaded pair (even though the
first available CPU id is on Socket 1).

In the "distributed" case, however, we want to ensure CPUs are allocated such
that we have an balanced distribution of CPUs across all NUMA nodes. This
points to allocating from Socket 1 if the only other CPU allocated has been
done on Socket 0.

To allow CPUs allocations to be packed onto full cores, one can allocate them
from the "distributed" algorithm with a 'cpuGroupSize' equal to the number of
hypthreads per core (in this case 2). We added an explicit test case for this,
demonstrating that we get the same result as the "packed" algorithm does, even
though the "distributed" algorithm is in use.

Signed-off-by: Kevin Klues <10df813f1921eff993d42337701788897067f836@nvidia.com>

csrwng/kubernetes,csrwng/kubernetes,bparees/kubernetes,bparees/kubernetes,bparees/kubernetes,openshift/kubernetes,bparees/kubernetes,csrwng/kubernetes,openshift/kubernetes,openshift/kubernetes,openshift/kubernetes,openshift/kubernetes,bparees/kubernetes,csrwng/kubernetes,csrwng/kubernetes