underlay: do not set link unmanaged by NetworkManager during provider network configuration

[zbb88888]

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

Examples of user facing changes:

• Bug fixes

Which issue(s) this PR fixes:

Fixes #(issue-number)

WHAT

🤖 Generated by Copilot at 03b11a1

Improve network configuration logging and error handling. Add log messages to init.go and avoid name swapping conflicts in ovs_linux.go.

🤖 Generated by Copilot at 03b11a1

Sing, O Muse, of the cunning code that swapped the names
Of ovs bridge and provider nic, to link them in the frame
But when the bridge was made before the nic was there
The code, with skill, avoided the redundant swap with care

HOW

🤖 Generated by Copilot at 03b11a1

• Add log messages to indicate provider nic configuration on OVS bridge (link, link)
• Avoid unnecessary name swapping between OVS bridge and provider nic (link)

[github-actions]

• Priority 1: In the InitOVSBridges() function, there is a missing error check after calling configProviderNic(). If an error occurs in this function, it will be returned to the caller without being handled. This could lead to unexpected behavior or crashes. It is recommended to add an error check and handle any errors that occur.
• Priority 2: In the ovsInitProviderNetwork() function, there is a missing error check after calling configProviderNic(). If an error occurs in this function, it will be returned to the caller without being handled. This could lead to unexpected behavior or crashes. It is recommended to add an error check and handle any errors that occur.
• Priority 3: In the configProviderNic() function, there is a redundant check for the prefix "br-" in the if statement. Since the function is only called with bridge names that start with "br-", this check is unnecessary and can be removed to simplify the code.
• Priority 4: In the configProviderNic() function, there is a missing error check after calling nmSetManaged(). If an error occurs in this function, it will be logged but not handled. It is recommended to add an error check and handle any errors that occur.
• Priority 5: In the configProviderNic() function, the error message returned by fmt.Errorf() does not provide enough context to diagnose the error. It is recommended to include more information about the specific error that occurred to aid in debugging.

[zbb88888]

[github-actions]

• The removal of the nmSetManaged function call in configProviderNic might cause issues with NetworkManager. It should be investigated if this function is still necessary and if so, it should be added back.
• There are inconsistent logging messages in InitOVSBridges and ovsInitProviderNetwork. They should be standardized to follow a consistent format.
• The fmt.Errorf calls in InitOVSBridges and ovsInitProviderNetwork should include more specific error messages to aid in debugging.
• The exchangeLinkName and macLearningFlag parameters in ovsInitProviderNetwork are not used and should be removed.
• The configProviderNic function could benefit from additional comments to explain its purpose and functionality.

[zbb88888]

需要回合到1.11