[Idea] Add workflow_call to more workflows

[jwikman]

Idea Description

I'd like to create an orchestrator workflow for our releases.
Draft thinking:

1. Identify which build to release
2. Construct input parameters for the other workflows that will be invoked
3. Invoke CreateRelease.yaml (creates pre-release)
4. Invoke a workflow that updates our Docs repo, in a work branch, creates a PR
5. Invoke PublishToAppSource.yaml (GoLive: false)
6. Manual gate approval - "Live on AppSource"
7. Update the pre-release created above and remove the "pre-release" flag
8. Run IncrementVersionNumber.yaml to increase minor version
9. Merge the Docs PR

But to be able to invoke other AL-Go workflows, they would need to have workflow_call added.

My other options:

1. Clone parts of above workflows (reusing actions), but that comes with quite a lot of maintenance debt.
2. use gh workflow run and poll for results
3. Hybrid of above

What's the downsides of adding workflow_call to the workflows?
One I can think about is when we need to add new required parameters, that could break callers. But that would break all my other options as well...

workflow_call got added to UpdateGitHubGoSystemFiles in #2031 (with an additional fix in #2154), but I would like to add this to more workflows.

I'm open to do the work myself, and in that case, I'd focus the three ones above.

Contribution (Optional)

• I would be open to contributing to this idea (implementation, documentation, testing, etc.)

[y0m0]

I also tried to achieve something similar and came to the same conclusion, we should have workflow_call on most of the workflows.