CPUManager policy option to align CPUs by Socket instead of by NUMA node

Starting with Kubernetes 1.22, a new CPUManager flag has facilitated the use of CPUManager Policy options(#2625) which enable users to customize their behavior based on workload requirements without having to introduce an entirely new policy. These policy options work together to ensure an optimized cpu set is allocated for workloads running on a cluster. The two policy options that already exist are full-pcpus-only(#2625) and distribute-cpus-across-numa (#2902). With this KEP, a new CPUManager policy option is introduced which ensures that all CPUs on a socket are considered to be aligned. Thus, the CPUManager will send a broader set of preferred hints to TopologyManager, enabling the increased likelihood of the best hint to be socket aligned with respect to CPU and other devices managed by DeviceManager.