Support nonexclusive NUMA nodes
NRM assumes that NUMA nodes are attached to containers in exclusive fashion; it will not attach the same node twice. This is actually not the default behavior of argo_nodeos_config, which attaches them non-exclusively.
Worse, if NRM runs out of NUMA nodes, it will still try to create a container, but with an empty NUMA node list. argo_nodeos_config used to accept such lists resulting in unusable containers, but that's fixed as of #baf8d886. NRM should be fixed not to generate such requests.
Ideally, we should extend the manifest to support both exclusive and non-exclusive NUMA node allocations.