Kayobe Ansible collection versions always take precedence over kayobe-config collection versions

[Scott Davidson]

If we have different versions of a collection defined in both kayobe/requirements.yml and in kayobe-config/etc/kayobe/ansible/requirements.yml (e.g. the stackhpc.linux collection) then the Kayobe version is used everywhere.

This can lead to difficult to track down errors e.g. in hook playbooks if import_role tasks such as

- import_role:
    name: <collection-name>.<role-name>

are used in the playbook.

Prioritising the collection version in kayobe-config, at least for custom hooks, would probably make more sense.

[Will Szumski (willjs)]

Mark pointed out at the PTG (https://etherpad.opendev.org/p/kolla-dalmatian-ptg) that it can be desirable to use custom collections for things like filters in your kayobe configuration, but it could be possible to arrange the precedence so that it went:

- kayobe custom playbook collections
- kayobe collections

for kayobe playbooks. That way you could have additions, but could not replace the plugins in the kayobe managed collections.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/kayobe/+/917762