Consider Entrypoint Workflow Requirements

[CodeGat]

In a similar vein to build-cd, we need to decide how Model Component Repositories (MCRs?) will interface with an updated build-ci.

Usually, we do this via Entrypoint Workflows, which are on.workflow_call-triggered workflows stored in build-ci. Also consider using Custom Actions.

Considerations

• An entrypoint workflow should contain a minimal amount of required arguments (preferably getting input via files stored on the Model Component Repository), defaults of which should be handled by the entrypoint workflow. This is so there are minimal major version updates to Model Component Repositories when the Entrypoint Workflows change.
• An Entrypoint workflow should consider multiple types of invocation - on.pull_request, on.push, on.workflow_dispatch...even on.repository_dispatch or webhook event. Usually, we have enough information within the existing contexts to handle what must be done for different triggers. Consider a defaults job that sets the required inputs regardless of trigger event.
• Output important information from these jobs. Don't discount the possibility that MCRs will have custom logic post-entrypoint workflow.