[alexadereyko]

Brief

Make stage.yml callable by the openDAQ bundle, which stages the module in its own run when the registry lacks it,
against a core from the registry or staged in the same run.

Description

• workflow_dispatch and workflow_call take ref, the commit to stage, and opendaq-ref, the core's (a sha,
  branch or tag; empty: the opendaq_ref file); workflow_call also takes exclude-jobs, the jobs the caller does
  not build.
• skip-staging-push keeps the staging out of the registry.
• staging-push names the identity of the stagings: idx-<sha256> of the commit and the core's, pkg-<sha256> of
  those and the triplet.
• include-jobs, staging-pull and packages are written out, no script. The core is pulled into
  opendaq-staging-<job>, as the core's stage names it, so a core already in the run is not pulled again; a pull
  for an excluded job is skipped.

Usage example

By hand, building only:

export WORKFLOW_REF=<branch | tag>    # the stage.yml run, e.g. main
export REF=<sha | branch | tag>        # the commit staged
export OPENDAQ_REF=<sha | branch | tag> # the core it is built against; empty: opendaq_ref
gh workflow run stage.yml -R openDAQ/MQTTStreamingModule --ref "$WORKFLOW_REF" -f ref="$REF" -f opendaq-ref="$OPENDAQ_REF" -f skip-staging-push=true

From the bundle, for its platforms only:

uses: openDAQ/MQTTStreamingModule/.github/workflows/stage.yml@main
with:
  ref: <sha | branch | tag>
  opendaq-ref: <sha | branch | tag>
  exclude-jobs: '["manylinux*", "windows-*-x86-*"]'

A staging is published by hand, unless "Build only" is ticked, and on schedule when the module and its core lie on
main or release/**. A run of another workflow, the bundle's (its workflow is not this one:
job.workflow_ref != github.workflow_ref), never publishes, whatever it passes: it may stage a temporary commit, of
a pull request for one.