iptables: use the same mode with kube-proxy

[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 submariner integration in ubuntu 22.04.

https://github.com/kubernetes-sigs/iptables-wrappers/blob/master/README.md

[github-actions]

• The commit message should be more descriptive and informative.
• There are no potential bugs or format errors in the code patch.
• It is unclear if there are any performance issues without further context.
• It would be helpful to include comments explaining the purpose of each function and variable.
• Consider using more descriptive variable names to improve readability.

[github-actions]

• The commit message should be more descriptive and informative.
• There are no potential bugs or format errors in the code patch.
• It is unclear if there are any performance issues without further context.
• It would be helpful to include comments explaining the purpose of each function and variable.

[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 diff.
• It is difficult to assess performance issues without further context on the codebase and the changes made.
• It would be helpful to include some examples or use cases for the changes made in the commit message.
• The patch could benefit from additional comments in the code to explain the reasoning behind certain decisions or to clarify any complex logic.

[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 diff.
• It is difficult to assess performance issues without more context about the code being changed.
• It would be helpful to include comments in the code explaining the purpose of each change and how it improves the code.
• Consider adding unit tests to ensure that the changes do not introduce new bugs or regressions.