Enable FF_USE_FASTZIP

What does this MR do?

The fastzip implementation provides a number of advantages for the CI cache:

1. Configurable compression levels: it appears that fastzip supports configurable compression levels, while the legacy ZIP implementation does not.

2. Avoids unnecessary cache uploads: normally symlinks are recreated after extracting the entire ZIP file, and this invalidates the CI cache because the last modified timestamps of the newly-created symlinks are later than the last modified timestamp of the ZIP file. The fastzip implementation ensures that symlinks are updated with the actual last modified timestamp, now that gitlab-runner#38960 (closed) has been resolved in GitLab Runner 18.3. Once we use a recent enough version, cache invalidation will happen far less frequently.

In my tests using an uploaded Ubuntu 22.04 cache archive that had 13 GB of data--mostly from the Omnibus cache (a Git bundle)--these were the benchmark results:

• Legacy ZIP: 2 min, 6 s, 12.0 GB
• fastzip (default compression): 2 min, 8 s, 12.0 GB
• fastzip (fastest compression): 1 min, 38 s, 12.7 GB
• fastzip (slowest compression): 4 min, 39 s, 11.9 GB

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• Latest Merge Result pipeline is green.
• When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

• The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
• If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
• If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
• If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes.
• Documentation created/updated.
• Tests added.
• Integration tests added to GitLab QA.
• Equivalent MR/issue for the GitLab Chart opened.
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.