[WIP] build/artefacts: Use zstd where possible

[phlax]

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

[repokitteh-read-only]

CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to (bazel/.*repos.*\.bzl)|(bazel/dependency_imports\.bzl)|(api/bazel/.*\.bzl)|(.*/requirements\.txt)|(.*\.patch).
envoyproxy/dependency-shepherds assignee is @RyanTheOptimist

🐱

Caused by: #29780 was opened by phlax.

see: more, trace.

[phlax]

this is generally a good idea - the only problem with it is that pkg_tar cannot currently (years long discussion 8/) consume zstd files so it can make the output ~unusable efficiently without some hackery

in this case i mostly wanted to do this for the docs output but i want it to be consumable in the website build so not really possible

i will update this - i think we can still use and get some reasonable benefit

[github-actions]

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!