NUMATopologyFilter should be supported by default or dedicated option (required for hugepages, cpu pinning)

[Trent Lloyd]

In order to use NUMA topologies, you need to add NUMATopologyFilter to the scheduler-filter list.

Currently the only way to do that is to supply the entire list which then presents a challenge for OpenStack upgrades as this list changes over time and the user then needs to try and synchronise those changes manually - for example the list has been changed for Victoria and Train onwards deprecated many of the currently set filters.

NUMA is required implicitly to use Huge Pages and CPU Pinning (commonly used features) or can also be requested explicitly using flavor extra specs or image metadata. Many deployments are using Huge Pages or CPU Pinning.

We should consider just adding this to the default list, or at least providing a config option to add it to the list without having to explicitly set the entire filter list to smooth upgrades.

My thinking is that it should be safe to enable this by default, as the docs state "If instance has no topology defined, it will be considered for any host. If instance has a topology defined, it will be considered only for NUMA capable hosts."
 https://docs.openstack.org/nova/ussuri/admin/configuration/schedulers.html)