Clean up vlan ip rules before setting up pod networks

[SaranBalaji90]

What happened:
When pods are deleted without TerminationGracePeriod, host veth devices for the pods using security group are not removed as Ipamd plugin will not be able to query APIServer for the deleted pod. Therefore when new pods are created, hostveth uses invalid vlan routing table.

What you expected to happen:
Before setting up new pods, clean up all existing vlan id from ip rule.

How to reproduce it (as minimally and precisely as possible):
By force deleting the pod using security group, ipamd leaves dangling resources in ip rules.

Similar to this -

amazon-vpc-cni-k8s/cmd/routed-eni-cni-plugin/driver/driver.go

Line 491 in 1c1d4b9

// 2. delete two ip rules associated with the vlan

we should perform clean up here to delete the hostVeth from ip rule 1b.

amazon-vpc-cni-k8s/cmd/routed-eni-cni-plugin/driver/driver.go

Line 316 in 1c1d4b9

// 1. clean up if vlan already exists (necessary when trunk ENI changes).