Feat(eos_designs): Support ESI for pe routers

[gmuloc]

Enhancement summary

Right now when using PE routers this line is blocking generation because PEs are not VTEP:

https://github.com/aristanetworks/avd/blob/devel/python-avd/pyavd/_eos_designs/structured_config/connected_endpoints/utils.py#L101

Which component of AVD is impacted

eos_designs

Use case example

interface Port-Channel1
   description L2_sw1-mrv499_Port-Channel1
   no shutdown
   bgp session tracker EVPN_SESSION_TRACKER
   switchport trunk allowed vlan 100
   switchport mode trunk
   switchport
   !
   evpn ethernet-segment
      identifier 0000:0000:a743:abac:5eae
      route-target import a7:43:ab:ac:5e:ae
   lacp system-id a743.abac.5eae
!

Describe the solution you would like

Relax the check to also accept this scenario

hacked like this for POC purposeS:

 if len(set(adapter["switches"])) < 2 or not self.shared_utils.overlay_evpn or not (self.shared_utils.overlay_vtep or self.shared_utils.overlay_ler):

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

• I agree to follow this project's Code of Conduct

[krikoon73]

From the services prospectives, in EVPN-MPLS context, there is 3 kind of services currently:

• e-line or pt-to-pt services (already available in eos_design)
• e-lan or pt-2-mpt L2 services => this is the purpose of this issue
  • EVPN MH support (A/A or A/S)
  • regular switchport interface support
  • l2 subinterface support with or without flex-encap
• l3 unicast services (already available in eos_design)