Feat(eos_designs): support multiple descriptions in connected_endpoint adapter rather than a unique one

[pvinci-arista]

Enhancement summary

add support for unique physical descriptions on the adapter level following the pattern used for L3_interfaces

Which component of AVD is impacted

eos_designs

Use case example

When configuring port-channel member interfaces, a unique description indicating the peer is desired.

Describe the solution you would like

add a new key under adapter

# `descriptions` has precedence over `description` | Optional
        descriptions: [ <description1>, <description2>, description3> ]

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

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

[github-actions]

This issue is stale because it has been open 90 days with no activity. The issue will be reviewed by a maintainer and may be closed