Refactor GH actions with reusable actions / workflows

[jabrah]

We should have one set of actions or workflows maintained in our main repo that can be used by other repositories to simplify maintenance. Such workflows and actions are still versioned, but the same actions won't need to be duplicated across code repositories

[jabrah]

I played around with this stuff a little bit and created two tiny repos to demonstrate extracting parts of a workflow into reusable GH actions, both hosted within the same repository and one in a different repository:

• https://github.com/jabrah/gh-actions-test : Has 1 action and the overall workflow that calls the reusable actions
• https://github.com/jabrah/my-custom-action : Has 1 other action

[jabrah]

#595

[jabrah]

May be able to separate the Java release workflows that upload release artifacts that the other Java release workflows can then download into the local .m2 repo for local resolution

https://github.com/actions/upload-artifact
https://github.com/actions/download-artifact

[jabrah]

PR #595 has an in-progress attempt at consolidating all PASS releases. Some issues need to be taken care of before this is ready to test:

• pass-ui, pass-auth, pass-acceptance-testing, pass-docker release workflows need to be updated to include on.workflow_call with appropriate inputs to call the workflows remotely
  • Need to check the behavior of each of these workflows checkout step. For example, when calling the pass-ui release workflow, will it checkout eclipse-pass/pass-ui or will it checkout eclipse-pass/main, since that's the repository that will call the release workflow?