Update packages with high CVE issues

[nwneisen]

This updates packages to fix the CVEs reported in #191

Running the scanner with these changes shows the reported CVEs are fixed.

(MKE-9731-fix-cves): trivy repo --branch MKE-9731-fix-cves https://github.com/nwneisen/cri-dockerd
2023-05-31T13:50:33.866-0600    INFO    Vulnerability scanning is enabled
2023-05-31T13:50:33.866-0600    INFO    Secret scanning is enabled
2023-05-31T13:50:33.866-0600    INFO    If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2023-05-31T13:50:33.866-0600    INFO    Please see also https://aquasecurity.github.io/trivy/v0.41/docs/secret/scanning/#recommendation for faster secret detection
Enumerating objects: 6990, done.
Counting objects: 100% (6990/6990), done.
Compressing objects: 100% (4675/4675), done.
Total 6990 (delta 2210), reused 5571 (delta 1894), pack-reused 0
2023-05-31T13:50:46.560-0600    INFO    Number of language-specific files: 1
2023-05-31T13:50:46.560-0600    INFO    Detecting gomod vulnerabilities...

[neersighted]

Looks like go mod vendor got missed 😅

[neersighted]

Looks like this is going to require some code changes for API movement; however skimming through the new vendor there's nothing that jumps out at me as being ripe for regressions.

[neersighted]

Looks like there's still some test failures to dig into related to seccomp profiles.

[nwneisen]

This looks like an error with the integration action in general. The same failure is happening on all of the other open PRs and master 👀

[neersighted]

Ah, good catch. I think we will have to follow-up on that later than. If the failures are not new, LGTM 👍

[nwneisen]

It looks like master previously passed and rerunning it now fails due to this issue. So this is a new issue with integration. I'm going to hold off on merging this and take a look at the problem now and I will open a fix in another PR