Refactor(eos_cli_config_gen): Move the dpath_enabled and domain ids under evpn gateway

[gmuloc]

Enhancement summary

In order to prepare for a better support for the RT/RD rewrite support this PR intends to move some keys around

Which component of AVD is impacted

eos_designs

Use case example

Describe the solution you would like

 <node_type_keys.key>:
   defaults:
     evpn_gateway:
       remote_peers:
         - hostname: <str; required; unique>
           ip_address: <str>
           bgp_as: <str>
       evpn_l2:
         enabled: <bool; default=False>
       evpn_l3:
         enabled: <bool; default=False>
         inter_domain: <bool; default=True>
+      d_path:     
+        # Enable D-path for use with BGP bestpath selection algorithm.
+        enabled: <bool; default=True>
+        # ASN(asplain):local_admin or ASN(asdot):local_admin notation
+        local_domain_id_local: <str; required>
+        # ASN(asplain):local_admin or ASN(asdot):local_admin notation
+        remote_domain_id: <str; required>
       all_active_multihoming:
         enabled: <bool; required>
-        # Enable D-path for use with BGP bestpath selection algorithm.
-        enable_d_path: <bool; default=True>
-        # ASN(asplain):local_admin or ASN(asdot):local_admin notation
-        evpn_domain_id_local: <str; required>
-        # ASN(asplain):local_admin or ASN(asdot):local_admin notation
-        evpn_domain_id_remote: <str; required>
         evpn_ethernet_segment: # required 
           # EVPN Ethernet Segment Identifier (Type 1 format)
           identifier: <str; required>
           # Low-order 6 bytes of ES-Import Route Target.
           rt_import: <str; required>

adjust the code to take into account these new keys in overlay

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

• I agree to follow this project Code of Conduct