qubes-ansible: It's easy to accidentally not use `qubes_proxy` in dom0

[HW42]

Qubes OS release

Qubes OS 4.3

Brief summary

If a user only installs qubes-ansible but not qubes-ansible-dom0 both the qubes_proxy strategy as well as the guard that prevents accidentally not using it is missing.

Steps to reproduce

1. Install qubes-ansible (but not qubes-ansible-dom0) in dom0.
2. Run a playbook against a VM, but do not enable the qubes_proxy strategy

Expected behavior

It should fail and inform the users that they must use the qubes_proxy strategy.

Actual behavior

Works without using qubes_proxy. See #10030 for why this is a problem.

Additional information

No response

[Atrate]

Would it be as simple as making qubes-ansible depend on qubes-ansible-dom0 for the host packages?