feat: workflow to validate and rename ports and port groups

[haseebsyed12]

Implement automated validation and synchronization of Ironic ports and
portgroups to ensure consistent naming conventions and proper representation
in Nautobot.

Problem:

• Ports and portgroups in Ironic were being created without node name prefixes,
  making it difficult to identify which node they belong to
• No automatic synchronization of portgroups (LAGs) to Nautobot
• Inconsistent naming conventions across the infrastructure

Solution:

1. Automatic Name Validation and Fixing:

   • Enforce $NODENAME:$INTERFACE naming convention (e.g., "server-123:bond0")
   • Automatically prefix port/portgroup names with node name when missing
   • Use colon separator for clear, unambiguous parsing

2. Nautobot LAG Synchronization:

   • Create LAG interfaces in Nautobot (type="lag") for Ironic portgroups
   • Strip node prefix for clean LAG names in Nautobot
   • Store bonding mode in interface description field
   • Sync MAC addresses and operational status

3. Event-Driven Architecture:

   • New Argo Events sensor for portgroup events (create/update/delete)
   • Reuse existing port sensor for port events
   • Workflows trigger on Ironic Oslo message bus events

[cardoe]

@stevekeay This will work with the rest of the code?