refactor(download-center-upload): use gcloud storage

[kellervater]

Replace gsutils -m cp with gcloud storage cp to be working appropriately with python >=3.12 which is installed on current ubuntu runner images (>= 24.04).

[kellervater]

This PR shall replace another PR to comply with general recommendations on how to work with gcloud storage.

It replaces gsutil with gcloud storage.

⚗️

Verified with a draft PR in camunda-modeler.

Following job steps seem to have worked just fine:

• https://github.com/camunda/camunda-modeler/actions/runs/11387491643/job/31682226077#step:9:80
• https://github.com/camunda/camunda-modeler/actions/runs/11387491643/job/31682225492#step:9:80
• https://github.com/camunda/camunda-modeler/actions/runs/11387491643/job/31682226682#step:9:80

Uploaded artifacts can be found here:

• https://console.cloud.google.com/storage/browser/downloads-camunda-cloud-release/camunda-modeler/nightly?pageState=(%22StorageObjectListTable%22:(%22f%22:%22%255B%255D%22))&project=camunda-public

Nonetheless, one seemingly unrelated workflow (Build MacOS Latest) fails.
@barmac It seems one unit test is failing here. Can you dismiss this problem? There's obviously a single unit test failing:

Chrome Headless 129.0.0.0 (Mac OS 10.15.7) <App> #checkFileChanged should NOT update file contents on cancelling FAILED
	AssertionError: expected spy to have been called at least once, but it was never called
	    at Context.eval (webpack-internal:///1281:1853:35)

@maxdanilov Can you please review the action change itself?

[maxdanilov]

The change LGTM, thank you! Interesting that there's nothing akin to the -m (parallelism) switch for gcloud storage - is it doing that by default?

[kellervater]

@maxdanilov
A bit down the documentation there's a hint in a different flag about it (Parallelism is default):

--continue-on-error, -c
If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This flag takes effect only in sequential execution mode (i.e. processor and thread count are set to 1). Parallelism is default.

[kellervater]

@barmac The initial failed run seems to be a wobbler. After a rerun the tests for macos-build succeeded.
So it seems to be fine.
Will merge this one now.