[aws] instance selection based on cpu, memory, nested-virt, etc. not working for default values of cpus, and memory

While using mapt the create operation exits with the following error:

DEBU running 'mapt aws rhel create'
DEBU context initialized for mapt7591cd5f
ERRO no instances matching criteria

while trying to use the ec2-instance-selection tool (https://github.com/aws/amazon-ec2-instance-selector) which is the library that mapt uses we get the following error:

% ec2-instance-selector --memory 64 --vcpus 8 --baremetal
NOTE: The criteria was too narrow and returned no valid instance types. Consider broadening your criteria so that more instance types are returned.

when providing the cpus, memory as the minimum value it works:

% ec2-instance-selector --memory-min 64 --vcpus-min 8 --baremetal
c5.metal
c5d.metal
c5n.metal
c6a.metal
c6g.metal
c6gd.metal
c6i.metal
c6in.metal
c7g.metal
c7gd.metal
c7i.metal-24xl
c7i.metal-48xl
c8g.metal-24xl
c8g.metal-48xl
g4dn.metal
i3.metal
i3en.metal
i4i.metal
m5.metal
m5d.metal
NOTE: 30 entries were truncated, increase --max-results to see more

We'll have to update our default values, and also consider using the cpus, memory as the minimum value while filtering

Start by reproducing the mapt AWS create failure and compare its default CPU and memory criteria with the ec2-instance-selector commands shown in the issue. Inspect the AWS create path and its instance-selection defaults; done means valid instances are selected for the defaults and the create operation no longer exits with "no instances matching criteria."