Reduce bond device names during migration from NethSecurity 7 to ensure HA compatibility

[cotosso]

Description
During migration from NethSecurity 7 to NethSecurity 8, bond device names are preserved in their original, longer form.
This differs from the naming convention used when bonds are created directly on NethSecurity 8, where shorter names are used.

This issue proposes automatically reducing bond names during migration so they are immediately compatible with NethSecurity 8 conventions and HA requirements, without manual intervention.

Why this is an issue
On NethSecurity 7, bond devices were typically named using longer identifiers, such as bond0, bond1, and so on.
On NethSecurity 8, bonds created from scratch use shorter names.

When migrating:

• Bond names are not aligned with NethSecurity 8 defaults
• Manual renaming may be required to meet HA constraints
• This increases the risk of misconfiguration and operational errors

Proposed solution
During migration from NethSecurity 7 to NethSecurity 8:

• Automatically reduce bond device names to two characters
• Generate the new name by taking the first and the last character of the original bond name

Examples:

• bond0 → b0
• bond1 → b1

This approach:

• Preserves a clear and deterministic mapping
• Matches the naming style used by bonds created directly on NethSecurity 8
• Ensures immediate compatibility with HA setups without manual changes

Affected version
NethSecurity 8.7.1

[gsanchietti]

The bond prefix is used in many parts of the migration script to know exactly what to do in some edge cases.
Changing the prefix will cause regressions.

The bond name can be changed later from the UI.

CANTFIX