Resolve SetLoadBalancerAffinityTimeout not being effective

[jiliangsui]

• 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 #(2462)

WHAT

🤖 Generated by Copilot at 2fd08a6

Update load balancer options with affinity timeout. This change modifies the pkg/ovs/ovn-nb-load_balancer.go file to set and store the affinity timeout option for load balancers in the OVN network backend.

🤖 Generated by Copilot at 2fd08a6

options map set
load balancer updated
autumn leaves fall

HOW

🤖 Generated by Copilot at 2fd08a6

• Set the affinity timeout option for load balancers in the OVN network backend (link, F

[github-actions]

• The commit message is missing. It should provide a clear and concise explanation of the changes made in this patch.
• There are no potential bugs or format errors in this patch.
• There are no performance issues in this patch.
• Instead of updating the lb.Options field directly, it would be better to create a new map and copy all the existing options into it before adding the new "affinity_timeout" option. This ensures that the original lb.Options map is not modified and can be used for other purposes if needed.

[jiliangsui]

@gugulee Please review

[gugulee]

can you write a unit test for this issue?

[github-actions]

• The commit message is missing. It should provide a brief description of the changes made in the patch.
• There are no potential bugs or format errors in the code diff.
• The performance of the code is not affected by the changes made in the patch.
• In the SetLoadBalancerAffinityTimeout function, the lb.Options field is updated with the new options map, but this is not necessary since the UpdateLoadBalancer function already updates the load balancer object with the new options. Therefore, the line lb.Options = options can be removed.
• In the testSetLoadBalancerAffinityTimeout function, the test case where the affinity timeout is added repeatedly seems redundant since it is testing the same functionality as the previous test case. This test case can be removed to simplify the test suite.

[github-actions]

• The commit message is missing, it should provide a brief description of the changes made in this patch.
• In the SetLoadBalancerAffinityTimeout function, the lb.Options assignment should be moved before the loop that populates the options map to avoid overwriting the affinity_timeout value.
• In the testSetLoadBalancerAffinityTimeout function, the test case should cover the scenario where an invalid timeout value is passed as input.
• In the testSetLoadBalancerAffinityTimeout function, the repeated test case should cover the scenario where the affinity_timeout value is removed from the load balancer options.

[oilbeater]

Thanks! @jiliangsui