Fix(eos_designs): Fix schema validation of dynamic keys

[ClausHolbechArista]

Change Summary

Fix schema validation of dynamic keys

The schema validation tooling did not have a way of populating the default values of dynamic keys lists like node_type_keys, so this was implemented manually before running validation.

The default values were loaded from shared_utils but since no validation had been done, shared_utils would fail badly if any input was not as expected.

[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-4474
# Activate the virtual environment
source test-avd-pr-4474/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/ClausHolbechArista/avd.git@fix/eos_designs/fix-schema-validation-of-dynamic-keys-lists#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/ClausHolbechArista/avd.git#/ansible_collections/arista/avd/,fix/eos_designs/fix-schema-validation-of-dynamic-keys-lists --force
# Optional: Install AVD examples
cd test-avd-pr-4474
ansible-playbook arista.avd.install_examples

[emilarista]

Tested with repo that broke node_type_keys, connected_endpoints_keys and network_services_keys. All faulty variables now result in proper schema validation type errors. LGTM!

[sonarqubecloud]

Quality Gate passed

Issues
2 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 SonarCloud