Feat(eos_cli_config_gen): Support STUN

[burnyd]

Change Summary

Add new CLI for STUN for eos devices.

It is possible and likely that many of the edge devices will be behind NAT devices. In order for a full mesh of connectivity to be created we need a method of determining the public IP / mapped port of each device. STUN serves this purpose. Each edge will initiate a stun request to the configured STUN server. The STUN server will then record the IP / Port mappings and import that information into BGP 1/79 to be shared with other devices in the network.

Component(s) name

arista.avd.eos_cli_gen

Proposed changes

Add stun for both client and server to eos cli gen

stun:
  server: 
    local_interface: ethernet1 
  client:
    - server_profile: server1 
      ip_address: 1.2.3.4
    - server_profile: server2
      ip_address: 2.3.4.5

Needed to separate both client and device since there are different possible cli knobs under each. It would render like the following..

stun
  server
    local-interface ethernet1
    client
        server_profile server1
         ip address 1.2.3.4
        !
         server_profile server2
         ip address 2.3.4.5

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.

[gmuloc]

Fixed the arista.avd.defined filters in templates for you. You would now need to add some test under the eos_cli_config_gen molecule scenario

[gmuloc]

servers are sorted alphabetically:
Before

leaf1#show run | se stun
stun
   client
      refresh interval 42 seconds
      !
      server-profile TEST
         ip address 42.42.42.42
      !
      server-profile TEST2
         ip address 66.66.66.66
   !
   server
      local-interface Ethernet42

Add ing the server-profile BLAH

leaf1(config-stun-client)#server-profile BLAH
leaf1(config-stun-server-profile)#show run | se stun
stun
   client
      refresh interval 42 seconds
      !
      server-profile BLAH
      !
      server-profile TEST
         ip address 42.42.42.42
      !
      server-profile TEST2
         ip address 66.66.66.66
   !
   server
      local-interface Ethernet42