Refactor workflows and implement combined Java module release

[markpatton]

Major changes:

• Add a workflow that releases all the Java modules together.
• Separate snapshot and release workflows that can be reused by other modules
• Add reusable actions for complicated scripts
• Handle case of sonatype push failing on closing the repo, but it actually succeeds
• Automatically wait for sonatype releases to appear in Maven Central
• Detect case of Maven Central release already existing and skip the release version deploy
• The release workflows also make a GitHub release

The release all Java modules workflow combines pass-core, and pass-support into one module on the file system such that maven can have everything in the reactor.

Testing resulted in two full releases being made, 1.3.0-RC1 and 1.3.0-RC2. The commits for those versions no longer exist because history was rewritten. The tags to those commits for the releases are no longer valid. After this pr is merged, the tags should be reset to that commit.

[jabrah]

Should we have the release and pass-java-release workflows run tests before build&deploy that can spike the run on failure?

[markpatton]

Should we have the release and pass-java-release workflows run tests before build&deploy that can spike the run on failure?

The deploy goal will automatically run the unit tests and integration tests so it will be spiked if they fail.

[jabrah]

looking good, quite a few interesting interactions when factoring in calls from other repos