Feat(plugins): Verify pyavd extras again in verify_requirements

[gmuloc]

Change Summary

Check again the sub requirements for pyavd[ansible-collection]

Component(s) name

plugins

Proposed changes

Read the metadata if any extras is detected and parse the markers.
It works also when running from source

How to test

Just install the PR and run it from source (using molecule) with -v as well as from one of your env where you install normally pyavd from git

Checklist

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)

[github-actions]

Review docs on Read the Docs

To test this pull request:

# Create virtual environment for this testing below the current directory
python -m venv test-avd-pr-4720
# Activate the virtual environment
source test-avd-pr-4720/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/gmuloc/avd.git@verify-pyavd-extra-reqs#subdirectory=python-avd" --force
# Point Ansible collections path to the Python virtual environment
export ANSIBLE_COLLECTIONS_PATH=$VIRTUAL_ENV/ansible_collections
# Install Ansible collection
ansible-galaxy collection install git+https://github.com/gmuloc/avd.git#/ansible_collections/arista/avd/,verify-pyavd-extra-reqs --force
# Optional: Install AVD examples
cd test-avd-pr-4720
ansible-playbook arista.avd.install_examples

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[carlbuchmann]

LGTM Tested:

• When running from source in AVD repo
• Installing from PR and example inventory