chore(deps): remove github.com/mholt/archiver/v3 dependency

[RTann]

mholt/archiver#396 has yet to land so github.com/mholt/archiver/v3 is still affected by CVE-2024-0406. This repository is not affected by this vulnerability.

This PR removes the dependency to:

• minimize dependencies
• ensure security scanners do not claim Scanner is affected, when it is not

Implementation is completely based on https://github.com/mholt/archiver/blob/v3.5.1/zip.go#L140.

Note: I want to make sure the diff-dumps still give the same data, but that step is failing at the moment... In any case, it doesn't hurt to start the review process

[RTann]

/retest

[RTann]

/retest

[RTann]

/retest

[msugakov]

This PR and subsequent scanner dependency update in stackrox/stackrox should help with https://github.com/stackrox/stackrox/security/dependabot/270

[dcaravel]

Looks like code was removed related to handling symlinks, was that because in the various workflows that use WriteZip we know symlinks are not being used?

(rest looks OK to me - holding approve for a successful diff-dump / test)

[RTann]

Looks like code was removed related to handling symlinks, was that because in the various workflows that use WriteZip we know symlinks are not being used?

Yes, WriteZip is only used by generate-dump and diff-dumps, and we do not use symlinks for either (that I know of).

(rest looks OK to me - holding approve for a successful diff-dump / test)

I'm also waiting for diff-dump. Running into space issues in CI, though it seems unique to this PR, so I wonder if I messed something up, I'm getting unlucky, or GHA allocates different resources for PR vs push to master branch

[openshift-ci]

@RTann: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/slim-e2e-tests	9635317	link	false	/test slim-e2e-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.