Consider supporting GC verb and STATUS verb added in CNI v1.2.0

[tnqn]

Describe what you are trying to solve

CNI v1.2.0 adds two new verbs:

GC verb
The GC verb allows runtimes to specify the set of known-good attachments, allowing plugins to clean up stale and leaked resources such as IPAM reservations. Libcni will also synthesize a CNI DEL for any stale cached attachments, so all users will have a form of GC, even if their plugins do not support CNI v1.1

STATUS verb
The STATUS verb allows a plugin to report its readiness to accept ADD requests. Runtimes such as containerd and cri-o will no longer have to rely merely on the presence of a CNI configuration file to determine network readiness.

If runtimes have supported them, we could consider implementing them to better integrate with runtimes.

[antoninbas]

It would be nice if GC was implemented for the host-local plugin.
It could essentially replace this custom code that we had to write: https://github.com/antrea-io/antrea/blob/main/pkg/agent/cniserver/ipam/hostlocal/gc.go
I opened an issue for this: containernetworking/plugins#1047

[github-actions]

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

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days. You can add a label "lifecycle/frozen" to skip stale checking.