Handle version mismatches in GHA

[jrw972]

Typically, the GitHub Actions for OpenDDS consists of a three-job chain where the first job is ACE/TAO, the second job is OpenDDS, and the third job performs the test.

The runner for each job is not guaranteed to be the same meaning the version of a dependency may change between the jobs.
This causes problems when the path to the dependency changes and is hard-coded.
For example, the path to java contains the version.
If the java version changes, then the path will also change and the path from one job cannot be reused from another job.

So, what needs to be done:

• Check that the image version recorded by the previous job matches the current job. Warn if there is a difference but continue the build because we expect the changes to be minor.
• Remove hard-coded paths from artifacts before they are uploaded. These should be replaced with something generic that would work in a downstream job. (Start with setenv and look for uses of the values).
• Remove cases where the version of a dependency is being used in GHA cache keys.
• Implement this concept for java, xerces, and openssl.

It is unclear if a compiler change from job to job causes a problem but should be considered.