Fix deletion of hostVeth rule for pods using security group

[couralex6]

Cherry picked from PR #1376

What type of PR is this?
bug

Which issue does this PR fix:
#1375
#1374

What does this PR do / Why do we need it:
This cleans up any dangling resources for old pods using same name. This might happen if pods are force deleted.

If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:

Testing done on this change:
Tested on dev cluster and verified the dangling rules are deleted before adding new routes.

[ec2-user@ip-192-168-65-167 ~]$ ip rule
10:	from all iif vlan.eth.1 lookup 101 
10:	from all iif vlan.eth.2 lookup 102 
10:	from all iif vlanaad671050aa [detached] lookup 101 
20:	from all lookup local 
[ec2-user@ip-192-168-65-167 ~]$ ip rule
10:	from all iif vlan.eth.1 lookup 101 
10:	from all iif vlan.eth.2 lookup 102 
10:	from all iif vlanaad671050aa lookup 102 
20:	from all lookup local 
[ec2-user@ip-192-168-65-167 ~]$ 

Automation added to e2e:
NA

Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No

Does this change require updates to the CNI daemonset config files to work?:
No

Does this PR introduce any user-facing change?:
No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.