Add CNI config 1.0.0 support.

[aznashwan]

This PR updates the containernetwork/cni dependency to 1.1.2 and adds support for reading CNI configs of up to 1.0.0.

Note that, although the "CHECK" verb had an entry point added for it it, it is currently no-op.

[aznashwan]

I am unsure why the 2022 runner is failing to find the main interface, as I have managed to successfully run it 5 times on my fork. (104, 105, 106, 107, and 108)

@debj1t could you please re-run the CI a couple more times so we can see whether it's an issue on this repo or transient to the runners.

[debj1t]

Thanks, for all the work!

[nicolaerosia]

@debj1t is there a way I can test this out? I would like to get an archive with the artefacts

[aznashwan]

@nicolaerosia back in December I had written this workflow running containerd's integration tests against the plugins.

Looking at one of my latest runs, the nat tests all ran fine and the sdnbridge ones were only failing at the PortMapping tests. (by default, the sdnbridge plugin does NOT create a gateway endpoint to allow the containers to reach the host)
sdnoverlay was blocked at initial network creation, however.

NOTE: there is a slight issue with the naming of the plugins not coinciding with the HNS network types, so you will need to also include this other PR in your testing. (it was the final blocker which prevented full integration with containerd before I left the project)

Hope this helped a bit, godspeed!

[slonopotamus]

Could you please make a release with these changes? It is required for nerdctl, see containerd/nerdctl#28 (comment)