fix(ewan-ace): standardize snip naming to match cross-JVD conventions

[KB-x]

What's New

Renames and splits 6 EWAN Advanced Core & Edge service/interface snips to align with the naming conventions established in MaaS and MEBS libraries.

• evpn-vpws-simple → evpn-vpws-vlan-based (matches MaaS precedent)
• evpn-elan-bridged / evpn-elan-simple → evpn-elan-vlan-based-irb / evpn-elan-vlan-based
• evpn-vpws-fxc → evpn-fxc-vlan-aware (distinct EVPN family, not VPWS sub-type)
• mac-vrf-elan split into evpn-elan-vlan-bundle + evpn-elan-vlan-based-irb (EVO)
• ccc-vpws-mux split into vlan-ccc-esi + vlan-bridge (distinct encapsulations)
• Portal snips.json regenerated (445 snips, 8 JVDs)

Why

Cross-JVD dependency and compatibility graphs rely on consistent naming families (service.evpn-elan, interface.ccc, etc.) to validate edges. The original EWAN ACE names used ad-hoc conventions that didn't match the regex families in the compatibility graph, making cross-JVD validation less reliable.

Details

• Renames: git mv for 6 service files (junos + evo), updated headers + Pair-with refs
• Splits: Combined multi-service files separated into individual snips (net +4 files: 47 to 51)
• Cross-references: ~15 files updated with new Pair-with back-references
• _variables.md: Updated with new canonical names
• Portal: snips.json regenerated, --check passing

Testing

• audit_library.py run: 51 snips, 0 errors, 0 warnings, 197 info (all expected)
• Dependency graph rebuilt: 428 snips, 1312 edges across 7 JVDs
• Compatibility graph regexes verified against new filenames
• Portal generate-snips.mjs --check passing