Feat(eos_designs): Build AVD topology from CloudVision I&T Studio data

[ClausHolbechArista]

Change Summary

Build AVD topology from CloudVision I&T Studio data

Component(s) name

arista.avd.eos_designs

Proposed changes

At first to be used with the studios integration, where the topology studio inputs resemble this cv_topology data model.
Depends on default_interfaces to determine the correct interface role.

---

CloudVision Topology.
Used to generate AVD configurations directly from the given topology if use_cv_topology is set to true.
Neighbor hostnames must match the inventory hostnames of the AVD inventory to be taken into consideration.
Requires default_interfaces to be set, to detect the proper interface roles automatically.
Currently providing the following configurations based on the given CloudVision topology and default_interfaces:

• uplink_switches.
• uplink_interfaces
• uplink_switch_interfaces
• mlag_interfaces
• # mlag_peer (future)
• platform
• mgmt_interface
  NOTES:
• Any derived configuration can be overridden by setting the key manually.
  Even keys set under node type defaults will take precedence over these derived configurations.
• when using parallel links between the same devices for L3 uplinks it is important to set
  max_uplink_switches and max_parallel_uplinks to ensure consistent IP addressing.

cv_topology:
  - hostname: <str>
    platform: <str>
    interfaces:
      - name: <str>
        neighbor: <str>
        neighbor_interface: <str>
use_cv_topology: <bool>

How to test

Updated an existing molecule scenario to ensure that the same config is generated without the manual inputs.

Checklist

User Checklist

• N/A

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)

[carlbuchmann]

LGTM