[FEA]: Make the Project Automation workflows reusable

[jarmak-nv]

Is this a new feature, an improvement, or a change to existing functionality?

Improvement

How would you describe the priority of this feature request

Medium

Please provide a clear description of problem this feature solves

Right now only the nv-morpheus/morpheus repo benefits from the project automations. Rather than copy-pasting the same automations into each repo and needing to maintain them separately, we should create a reusable workflow and then call it in each repo.

Describe your ideal solution

The nv-morpheus/utilities repo gets the reusable workflows and each repo calls them

• nv-morpheus Org
  • morpheus
    • calls workflows
  • utilities
    • houses workflows
    • calls workflows
  • mrc
    • calls workflows
  • morpheus-experimental
    • calls workflows
  • morpheus-viz
    • calls workflows

Additional context

The nice thing is there's no logic change between the workflows at all, so we can make the existing env variables into default input variables and not even need to supply them in the caller workflows.

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request

[jarmak-nv]

Suggestion from @cwharris - open a new repo for reusable workflows to prevent utilities from getting too cluttered and having a focused location for these, and potential future reusable workflows.

I like this approach for his reasons, and because it does feel awk having utilities be the only repo that both houses and calls the workflows.