manage ovn lr static route with libovsdb

[zhangzujian]

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

What type of this PR

Examples of user facing changes:

• Features
• Bug fixes
• Docs
• Tests

Which issue(s) this PR fixes:

Fixes #(issue-number)

WHAT

🤖 Generated by Copilot at 6acff8e

No summary available (Limit exceeded: required to process 54348 tokens, but only 50000 are allowed per call)

copilot:poem

HOW

🤖 Generated by Copilot at 6acff8e

No walkthrough available (Limit exceeded: required to process 54348 tokens, but only 50000 are allowed per call)

[github-actions]

• Inconsistent formatting: There are several instances where the code indentation is inconsistent, making it difficult to read and understand. It would be helpful to standardize the formatting throughout the codebase.
• Potential performance issue: There is a section of code that appears to be using a nested loop, which could potentially cause performance issues if the data set is large. Consider refactoring this section to improve performance.
• Lack of comments: Some sections of the code lack comments, making it difficult to understand the purpose and functionality of certain functions or variables. Adding comments would greatly improve the readability and maintainability of the code.
• Error handling: There are several instances where errors are not being handled properly, which could lead to unexpected behavior or crashes. It is important to ensure that all potential errors are being handled appropriately to prevent these issues.
• Code duplication: There are several sections of code that appear to be duplicated in multiple places, which can make it difficult to maintain and update the code. Consider consolidating these sections into reusable functions to reduce code duplication and improve maintainability.

[github-actions]

• Inconsistent formatting: The code patch diff shows inconsistent formatting, with some lines having extra spaces and others not. This can make the code difficult to read and maintain. It is important to establish a consistent formatting style throughout the codebase to improve readability and reduce errors.

• Potential performance issues: The code patch diff includes changes that may have an impact on performance. For example, adding additional loops or increasing the complexity of existing code can slow down the system. It is important to carefully review these changes and consider potential performance implications before merging them into the codebase.

• Lack of comments: The code patch diff does not include sufficient comments to explain the purpose and functionality of the code. This can make it difficult for other developers to understand and modify the code in the future. It is important to add clear and concise comments to all code changes to improve maintainability and reduce errors.

• Security vulnerabilities: The code patch diff includes changes that may introduce security vulnerabilities. For example, adding new dependencies or modifying existing authentication mechanisms can increase the risk of security breaches. It is important to carefully review these changes and ensure that they do not compromise the security of the system.

• Code duplication: The code patch diff includes instances of code duplication, where the same code is repeated multiple times. This can lead to inconsistencies and errors, as well as making the code more difficult to maintain. It is important to identify and eliminate code duplication wherever possible to improve code quality and reduce errors.