Fix(eos_designs, eos_cli_config_gen): Fix the AVD version print in virtual environments

[tgodaA]

Change Summary

ansible-galaxy collection list fails sometimes if the ansible collections path is not loaded properly. Even after the collections path is set properly in ansible.cfg, it still fails in few virtual environments. So providing the collections path is safer, ansible-galaxy collection list -p < collections_path >

Related Issue(s)

Fixes #1874

Component(s) name

Proposed changes

ansible-galaxy collection list -p COLLECTIONS_PATH

How to test

Tested locally on a virtual environment, to see if the correct collection version is printed or not.

Checklist

User Checklist

• Test this fix in a virtual environment and verify if the correct AVD version is printed

Repository Checklist

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and documentation have been updated accordingly.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[ClausHolbechArista]

The purpose of the version task is to see how ansible utilities pick up the various envrironment variables and configurations. So IMO we should not override the default check, since that would produce different results than running the tools directly.

[tgodaA]

I didn't override anything here. The collection_path is picked from the anisble var collection_path itself. I am not manually giving any input. If the collection_path is wrong then everything is wrong by default as the collection_path is calculated in this step.

[ClausHolbechArista]

LGTM

[carlbuchmann]

LGTM!