Add range support for Vxlan vlan vni mapping under interface vxlan 1

[Vicky-POC]

Enhancement summary

Be able to configure a range of vlan mapped to a a range of vni for the vxlan-vlan-vni mapping CLI. Currently the command only takes only a single vlan and a single vni value per line.

Which component of AVD is impacted

eos_cli_config_gen

Use case example

interface vxlan1
vxlan vlan 1001, 2001-3000 vni 11001, 12001-13000

Describe the solution you would like

vlans

• id String
  vni String

"id" can be a single VLAN-ID or a range of VLANs or comma separated list
"vni" can be a single VLAN-ID or a range of VLANs or comma separated list

Describe alternatives you have considered

stdpoc_custom_eos_cli: |
interface Vxlan1
vxlan vlan 1001, 2001-3000 vni 11001, 12001-13000

Additional context

In our job function, we frequently need to show configuration via CLI during a discussion. With more than one 1K of vlan-vni mapping defined in our environment, the configuration is very big. We have to do grep to find the right CLI. It will be so much more efficient to be be able to show the output of interface vxlan1 with just a few lines and talk about it. Also, with bigger files, any change, even just one line, pushes the change to CVP is taking a long time.

Contributing Guide

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

[ClausHolbechArista]

The change here would be to change the type of the id and vni fields to strings with auto-conversion from int and update the description as suggested.