T8329: Fix interface naming for Azure VF interfaces with Accelerated Networking enabled

ROOT-CAUSE:
Some Azure VF interfaces miss to get renamed leading to errors in the downstream rules and mess up with the interface names.
Two main problematic scenarios were found which prohibited the renaming of a VF interface to vf_ethN:
1. Missing udev add event, when change event is received directly
2. A VF interface registering during rootfs stage

FIX:
Rule 63:
-Azure VF naming is now handled by a dedicated helper - vyos_vf_name to provide collision-free names for VF interfaces. The helper vyos_vf_name would be packaged into initramfs so the same behavior works in early boot and normal boot (a separate PR).
-Rule 63 is now guarded to prevent recursive renaming of VF interfaces.

Rule 65:
-A fallback VF rename path has been added for any leftover VF interfaces that were missed to be renamed due to some unexpected situation. Those VF interfaces are renamed prior to running persistent renaming of synthetic interfaces. This prevents VF interfaces from being considered as synthetic interfaces which may lead to errors in the flow of execution.
-Rule 65 is now guarded so generic persistent naming does not override VF names.

0 files changed, 0 insertions, 0 deletions