Feat(eos_designs): vtep_diagnostic - fallback to loopback_ip_range if no matching loopback_ip_pools

[pvinci-arista]

Enhancement summary

The current behavior is to ignore loopback_ip_pools if loopback_ip_range is defined. This request is to change the functionality to use loopback_ip_range if there is not a corresponding pod_name entry for a host.

Which component of AVD is impacted

eos_designs

Use case example

It is a valid campus design to support border leafs that connect to a set of super spines. In this configuration, the border leafs do not belong to a pod, but still need a vtep_diagnostic address.

Describe the solution you would like

Use loopback_ip_range as a fallback if there is not a corresponding pod_name entry for a host.

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

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

[ClausHolbechArista]

This would be a breaking change, since some users may use this to control whether to generate the loopback. We cannot implement it until 6.0. I will add it to the milestone.
In your case you could set pod_name: border or similar.