perf: Speed up creating archives when pusing big codebases

[matyascimbulka]

This PR somewhat relates to #982. The main goal is to speed up creating ZIP archives for codebases larger than 2MB when using apify push.

The issue was in using archive.glob() function within the loop. This approach forces the library to go through the entire current working directory (and its children). Using this function is also redundant because the getActorLocalFilePaths already uses globby to get all of the valid file paths to be archived.

This issue is easy to measure while working on a generic actor for eu-monitoring-tool which has roughly 1200 source code files and large node_modules.

Here is comparison of the compression times:

• without fix: 137s
• with fix: 6s

@B4nan or @vladfrangu Could you please have a look?

[B4nan]

looks good to me, lets wait for Vlad before merging. i guess you tested this in the mentioned eu project, so you know it works. a test would be nice, but not crutial, we use the CLI beta for e2e tests in crawlee, so we should be warned in case things fall apart

[matyascimbulka]

@B4nan Thanks for the review. I agree that having a test would be better but the EU project code lives in topmonks organisation. So I'm not sure how to demonstrate it.

[vladfrangu]

well, if you tested it with your codebase / can test it with the built binaries from CI, and confirm it works the same way, we can merge it

[matyascimbulka]

How do I get the binaries for the CI so I can test them?

[vladfrangu]

You can find them here: https://github.com/apify/apify-cli/actions/runs/21478914434/attempts/1?pr=1011 at the bottom of the page, or by visiting the Check / Bundles step for your system and checking the logs for the artifact download URL!

Unix (mac/linux): https://github.com/apify/apify-cli/actions/runs/21478914434/artifacts/5303421975
Windows: https://github.com/apify/apify-cli/actions/runs/21478914434/artifacts/5303418966