make vpc_nat_gateway redo eip fip snat dnat iptables rules after k8s cluster reboot

[wenwenxiong]

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

WHAT

🤖 Generated by Copilot at b54535b

This pull request improves the reliability and consistency of the NAT gateway controller and the FIP feature. It adds logic to handle pod restarts and redo iptables rules for EIP, FIP, DNAT, and SNAT objects. It also changes the default value of the pod-default-fip-type flag to "iptables" and adds a function to initialize the VPC NAT gateways.

🤖 Generated by Copilot at b54535b

Sing, O Muse, of the skillful coder who changed the flag
Of pod-default-fip-type to match the docs and logic,
And who added to the controller the function initVpcNatGw
To initialize the gateways of the clouds, like Zeus the thunderer.

HOW

🤖 Generated by Copilot at b54535b

• Change the default value of the pod-default-fip-type flag to "iptables" to match the documentation and code logic (link)
• Add a function call to initialize the VPC NAT gateways in the controller's initResourceOnce function (link)
• Implement the initVpcNatGw function to list and enqueue the VPC NAT gateways for initialization and check their annotations (link)
• Import the time package to parse and compare timestamps for the EIP, FIP, DNAT, and SNAT configurations (link)
• Add logic to check the redo time and start time of the EIP, FIP, DNAT, and SNAT configurations in the handleAddIptablesEip, handleAddIptablesFip, handleAddIptablesDnatRule, and handleAddIptablesSnatRule functions, respectively, and reconfigure them if needed (link, link, link, link, link, link, link)

[oilbeater]

@wenwenxiong hi, are you still working on this pr?

[bobz965]

@wenwenxiong hi, are you still working on this pr?

if not, I will go on finish this pr.

[wenwenxiong]

i am not to do with this pr now