replace port_group function call with ovnClient

[gugulee]

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

What type of this PR

Examples of user facing changes:

• Features

Which issue(s) this PR fixes:

#2453

WHAT

🤖 Generated by Copilot at 74be2f5

This pull request refactors the port group management logic in various controllers, using the new ovnClient instead of the old ovnLegacyClient and the ovn-nbctl command line tool. This improves the performance, consistency, and simplicity of the network policy and security group operations.

🤖 Generated by Copilot at 74be2f5

Sing, O Muse, of the mighty ovnClient, the swift and skillful tool
That replaced the old and cumbersome ovnLegacyClient, the source of many a woe
And how the valiant coders, with wisdom and courage, refactored the port group code
To make it simpler, faster, and more consistent, like the arrows of Apollo

HOW

🤖 Generated by Copilot at 74be2f5

• Replace the ovnLegacyClient with the ovnClient for port group operations, and pass externalIDs to the CreatePortGroup method to store metadata (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
• Simplify the logic to check and add ports to the port groups, and remove the unused functions to list and map the logical switch ports and port group ports (link, link, link, link)
• Change the way to generate and use the port group names for network policies, using the np.Name field instead of the npName variable (link, link)
• Initialize and populate a map to store the network policy and node port group names in gc.go, to avoid duplication and improve lookup efficiency (link, link, link)
• Remove an empty line in node.go to improve code style (link)
• Change the way to report the error messages, using a more concise and consistent format (link, link, link, link, link)

[github-actions]

• The commit message should be more descriptive and informative. It should clearly state what changes were made and why.
• There are no potential bugs or format errors in the patch diff.
• It is difficult to assess performance issues without further information about the code being modified.
• Ways to improve could include adding comments to the code for clarity, refactoring repetitive code, or optimizing algorithms if applicable.