[BUG] Orchestrator is not taking into account the limitation that the macvms have when deciding where to create them

[cjlapao]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When trying to create more than 2 mac VMs, the orchestrator only looks into the disk, memory, CPU requirements and does not look into the limitation that only 3 mac VMs are allowed per host.

Expected Behavior

The orchestrator will take that into account before selecting the endpoints where the Vms needs to be created

DevOps Service version

v0.9.9

Relevant log output

ec2-user@dropsuite-mac-09f57f64650b70fc8 ~ % prlctl list -a
UUID                                    STATUS       IP_ADDR         NAME
{e3ce7c31-aca3-438a-ba68-bda878ed0bcc}  stopping     -               mkulka-coder-another
{d43b7f99-51ce-4486-9c9f-a8c18a9962d0}  running      -               mkulka-coder-test-hash
{70f78c06-7cc5-4c32-91b3-fd2804ffde0a}  running      -               mkulka-coder-test-nohash

Steps To Reproduce

not necessary

Anything else?

No response

Validation

• Yes, I've included all of the above information (Version, settings, logs, etc.)