Trigger presubmit ci workflows from ci.yml via workflow_call.

[ScottTodd]

History

These workflow jobs were originally part of ci.yml but they were moved out of part of #17957.

Reasons to keep them separate

• Run history for each workflow is independent, e.g. https://github.com/iree-org/iree/actions/workflows/ci_linux_x64_clang.yml and https://github.com/iree-org/iree/actions/workflows/ci_windows_x64_msvc.yml.
• Performance metrics for each workflow are independent:
• Status badges are independent

Reasons to merge them back

• Less code duplication, particularly for setup and summary steps (see Share workflow failure alerting between ci.yml and pkgci.yml. #19444)

• Less noise in the checks view in pull requests (note all the setup jobs, and the PR above will add similarly dupliated summary jobs):

• Centralized logs for checks, not split between multiple pages like they are currently:

  Current	With this PR

• This gives us a single ci_summary check in ci.yml to set as a required check instead of multiple split across workflows

• Given enough runner capacity / budget, we could run all these jobs on presubmit/postsubmit and not just on nightly schedules

[ScottTodd]

I'm on the fence with this. I think it improves the experience on pull requests but it makes monitoring more complicated. I think with custom queries we can look up job statistics within workflow runs to build our own metrics though.

Thoughts, @iamakanshab @Eliasj42 @amd-chrissosa @marbre ?

[marbre]

I think it is reasonable to move this back to invoke from ci.yml and have the impression that at least the manual monitoring via the GH UI doesn't get worse. However, I don't know about more automated monitoring.