[OPS 293] multiversion maven repo

[alourie]

Description

We've been building a pipeline container with superpom dependencies as a local Maven repo, which theoretically improves build times for the dependent projects. However, many projects are not up to date with the latest superpom, resulting in a dependency chain with a number of different superpom version, and hence "cache misses" for the packages.

This change will layer the dependencies from multiple superpom releases in the same local Maven repository, which should result in less cases of dependent packages missing during the following Maven builds.

Associated tasks

DO NOT MERGE UNTIL the following is merged a new pipeline-java is built:

• [OPS 292] Add labels to the resulting images ci-utils#23

Checklist

If any of these are not applicable, strikethrough the line ~like this~. Do not delete it!. Let the reviewer decide if you should have done it.

Code

• I have performed a self review of my own code (including checking issues raised when creating the PR).
  - [ ] I have added/updated unit tests for these changes, and if not I have explained why they are not necessary.
• I have commented my code in any hard-to-understand or hacky areas.
• I have handled all new warnings generated by the compiler or IDE.
• I have rebased onto the target branch (usually main).

Documentation

• I have updated the changelog.
• I have updated any documentation required for these changes.

Breaking Changes

• I have considered if this is a breaking change and will communicate it with other team members if so.

This is not a breaking change, and should automagically work with all other workflows.

[ryanjcoleman]

Task linked: OPS-293 Update superpom container build flows to include all the necessary use cases

[alourie]

I believe this is ready for an additional review and hopefully a merge.

[charlta]

With no way to manually/locally confirm this is working, it will be a matter of merge it and fix anything that goes wrong.

At time of approval the associated task was not been merged, and no new pipeline-java has been built, so make sure that happens before merging.