Set up GitHub Actions to automate output QC/QA & server updates

Several CCISS workflow (and subworkflows) outputs need to be checked for consistency with one another and then uploaded to different cloud servers.
Bellow is a "QC workflow" that needs to be triggered everytime one of the objects with checkmarks is changed:


Once the QC workflow completes successfully, it should trigger a second workflow that uploads a target object (not necessarily all the objects with checkmarks above) to cloud server ("uploading workflow"). Bellow is an example of an uploading workflow with feasibility tables:


Notes:
- Both the QC workflow and uploading workflow are implemented as GHActions.
- The QC workflow needs to happen across several GH repos (any repo that alters a checkmarked object).
- The QC will be implemented as an FFEC action (because it's essentially the same across many GH repos) - an FFEC actions repository will need to be created
- The uploading workflow will happen in repos that _host data_ (e.g. bcgov/SS_feasTable repo).*
- QC workflow will need to download objects to be checked from where they were uploaded to - objects cannot be large.

\* workflows that produce large datasets (e.g. BGC projections) automatically upload them to cloud servers, no GHActions needed.

The issue names no concrete files, so begin by inspecting the example uploading workflow in bcgov/SS_feasTable and mapping the repositories that alter the checkmarked objects. Trace where those objects are uploaded and how they can be downloaded for QC. Done means a reusable QC workflow runs across the relevant repositories and a successful QC run triggers the intended server upload.

Written by the indexing model from the issue text.