Feat(eos_designs): Support for PIM RP access_list_name under VRFs and Tenants

[jonxstill]

Change Summary

Support use of access_list_name under VRFs and Tenants, in a similar way to underlay_multicast_rps.

Related Issue(s)

Fixes #2881

Component(s) name

arista.avd.eos_designs

Proposed changes

Data Model:

< network_services_keys.key_1 >:
  < tenant_a >:
    pim_rp_addresses:
      - rps:
          - <str>
        groups:
          - <str>
        access_list_name: <str>
    vrfs:
      < tenant_a_vrf_1 >:
        pim_rp_addresses:
          - rps:
              - <str>
            groups:
              - <str>
            access_list_name: <str>

Behaviour is identical to that in #2846:

List of groups to associate with the RP addresses set in 'rps'.
If access_list_name is set, a standard access-list will be configured matching these groups.
Otherwise the groups are configured directly on the RP command.

How to test

Molecule tests modified to cover this case.
If you have an existing RP config on your PEGs you should be able to add the access_list_name key to an existing RP entry (value is the name of the ACL) and instead of specifying the groups on the rp address command, the generated config should refer to the ACL, which should contain the same groups that were configured on the rp address command.

Checklist

User Checklist

• N/A

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.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[perimore]

Tested this and works as expected.

[ClausHolbechArista]

Merging since @perimore also tested and approved.