Refactor: Address ansible 2.20 deprecation warnings showing

[gmuloc]

When running molecule converge -s ansible_only the following deprecation warnings show up:

TASK [arista.avd.eos_designs : Set eos_designs facts] **************************
[WARNING]: Deprecation warnings can be disabled by setting `deprecation_warnings=False` in ansible.cfg.
[DEPRECATION WARNING]: Direct access to the `_loader` internal attribute is deprecated. This feature will be removed from ansible-core version 2.23. Use `copy_with_new_env` to create a new instance.
[DEPRECATION WARNING]: Direct access to the `environment` attribute is deprecated. This feature will be removed from ansible-core version 2.23. Consider using `copy_with_new_env` or passing `overrides` to `template`.
[DEPRECATION WARNING]: The `ansible.module_utils.common._collections_compat` module is deprecated. This feature will be removed from ansible-core version 2.24. Use `collections.abc` from the Python standard library instead.
[DEPRECATION WARNING]: Importing 'to_text' from 'ansible.module_utils._text' is deprecated. This feature will be removed from ansible-core version 2.24. Use ansible.module_utils.common.text.converters instead.
[DEPRECATION WARNING]: Importing 'to_native' from 'ansible.module_utils._text' is deprecated. This feature will be removed from ansible-core version 2.24. Use ansible.module_utils.common.text.converters instead.

we should address them

ansible [core 2.20.2]
  config file = None
  configured module search path = ['~/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = ~/.venv/lib/python3.13/site-packages/ansible
  ansible collection location = ~/.ansible/collections:/usr/share/ansible/collections
  executable location = ~/.venv/bin/ansible
  python version = 3.13.11 (main, Jan 27 2026, 23:31:20) [Clang 21.1.4 ] (~/.venv/bin/python3)
  jinja version = 3.1.6
  pyyaml version = 6.0.3 (with libyaml v0.2.5)

[gmuloc]

The last three warnings are comming from ansible.utils. they have been addressed in
ansible-collections/ansible.utils#423 but there have been no release with the fix yet.

So they are not coming from AVD, nothing to do for us.
We are using ansible.utils filters in ansible_only molecule scenario and that's why we are seeing them there.
Once a new ansible.utils version is released we can redirect people to this.

I will fix the first two warnings in a PR.