[CBM] collect-logs on GCP may take much longer than expected

What's the issue?
Arun noticed while collecting logs for a GCP archive that it was taking an unreasonable amount of time (to the point where the process had to be killed).

This certainly should not be the case, in theory log collection should take a fairly consistent amount of time, since we perform the following basic steps:

1) Populate the staging directory (in this case it should have already been populated)
2) Collect some system information (with runs commands which in total run for ~30s)
3) Collect some files e.g. the plan
4) Write those into a ZIP file
5) Optionally redact some information

Arun noted that this behavior worked for S3 a few moments later.