Upgrade CNI plugins from v1.3.0 to v1.4.0

[luolanzone]

CNI plugin released v1.4.0 with golang 1.21, we can fix more CVEs with a newer golang version.

No need to maintain our own built CNI binary in short term. Fixes #5763
We probably can try to raise an issue first in the CNI binary repo to ask for a new release in the future if a similar case happened.

[antoninbas]

/test-all
/test-windows-all

[antoninbas]

@luolanzone I forgot that you will need to trigger a build of antrea/base-windows first, before we can merge this
You can do it yourself by running this workflow (https://github.com/antrea-io/antrea/actions/workflows/docker_update_base_windows.yml) and use your fork & branch as input parameters.

[luolanzone]

@luolanzone I forgot that you will need to trigger a build of antrea/base-windows first, before we can merge this You can do it yourself by running this workflow (https://github.com/antrea-io/antrea/actions/workflows/docker_update_base_windows.yml) and use your fork & branch as input parameters.

Hi, @antoninbas thanks for reminder, I triggered the workflow, but looks like it has a problem to get the Windows cni file from github, I tried in a linux host, download works fine. I will rerun the workflow later.
Meanwhile, I was not sure if "git/https" should be in the repo parameter, it take me a little time to figure out what's the format should be. So I submitted a PR #5816 to update the workflow description, please help to review. Thanks.

[tnqn]

@luolanzone is the mergeable?

[luolanzone]

Hi, @tnqn it's not ready to merge, the Windows base image workflow still failed, Not sure why the curl command on github Windows runner to get the cni binary is so unstable. I had rerun a few times but no luck yet. https://github.com/antrea-io/antrea/actions/runs/7269844266. I will update here if the base image is ready.

[luolanzone]

@tnqn , this PR is merge-able now. The base images are updated via this manual workflow build https://github.com/antrea-io/antrea/actions/runs/7354252963/job/20021229050. There is something wrong with curl command, after I replaced it with Windows build-in command 'Invoke-WebRequest', the build can pass. The root cause of curl failure is still not clear yet. I will submit a separate PR to update the Dockerfile to use 'Invoke-WebRequest' to build base Windows images considering it's not used frequently.