Background
Initially, some reusable workflows were created under the assumption that they would contain multiple jobs that needed to be matrixed together (eg. deploy-1-setup.yml -> deploy-2-start.yml, ci-closed.yml -> undeploy-1-start.yml).
However, this has not eventuated, and due to how GitHub Environments are scoped to a single job rather than a workflow, they probably won't be.
This means that we can collapse some levels of reusable workflows, reducing LOC and unneeded creation/pulling of artifacts from other reusable workflows.
Background
Initially, some reusable workflows were created under the assumption that they would contain multiple jobs that needed to be matrixed together (eg.
deploy-1-setup.yml->deploy-2-start.yml,ci-closed.yml->undeploy-1-start.yml).However, this has not eventuated, and due to how GitHub Environments are scoped to a single job rather than a workflow, they probably won't be.
This means that we can collapse some levels of reusable workflows, reducing LOC and unneeded creation/pulling of artifacts from other reusable workflows.