create a "wrapper" action to upload to crowdin and then download

[ElliotFriend]

Similar goal to #1990, but a different approach. not sure if one is better or more suited than the other, though. wanted to put it out there to get some eyeballs on it

The fix involves specifying a permissions block at either the root of the workflow or for each job (here, setting it at the root is recommended as both jobs are simple triggers of reusable workflows and likely need very few permissions). Ordinarily, workflows that trigger other workflows do not require write permissions; they only need minimal contents: read, unless the downstream workflow needs more. Adding the following block right after the workflow name sets the least-privilege permissions for all jobs in the workflow:

permissions:
  contents: read

This change should be added after the name: field and before the on: block to match typical GitHub Actions conventions.

The fix is to add a permissions key at the root of your workflow file .github/workflows/crowdin-manual-workflow.yml. Since this workflow primarily coordinates uploads and downloads through reusable workflows, and likely does not itself require write-level repository permissions, you should explicitly set minimal privileges. Unless the workflow directly creates pull requests, pushes changes, or interacts with issues, contents: read is a safe default permission. If later you discover that more granular permission (e.g., pull-requests: write) is necessary for these jobs, you can add it, but starting with a root-level read-only permission is best. Insert the following block under the name line (after line 1).

[stellar-jenkins]

Preview is available here:
http://developers-pr2004.previews.kube001.services.stellar-ops.com