Fix IPAM Leak

[neaggarwMS]

Details are found in ICM# https://icm.ad.msft.net/imp/v3/incidents/details/194727242/home

Fix:
Ensure even in failure cases, we release the pool when the IP is not in use.

Solution:
To accomplish that, we will be adding the container ID to the IPAM state file. Thereby if CNI ADD fails, it will still be able to delete any dangling state in the initial ADD call during the subsequent DELETE.

Also, add more calls to release pool/address in the CNI delete call. Such as if Endpoint is not found, network is not found etc.

[DreamRivulet]

@neaggarwMS May I know when there is a PR for this issue ?

[aegal]

@DreamRivulet the potential fix is linked.

[zhiweiv]

Do you know when will this be released? We got ip leak couple times recently.

[zhiweiv]

@tamilmani1989
#640 was merged to master long time ago, but it never appear in release notes, do you know why.

#755 also fixes ip leak issue, are they conflict?

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

[github-actions]

Issue closed due to inactivity.