Supporting Maven 2 meta versions

Maven 2 had metaversions "LATEST" (snapshot and non-snapshot latest - similar to latest.integration) and "RELEASE" (non-snapshot latest - similar to latest.release).

Its deprecated now but there are still some poms out there that use RELEASE or LATEST and transitive dependency versions.

In particular I have seen the following scenario:

library_a --- depends import scope --> library_b:RELEASE

So now if I add library_a as a dependency in my project, it looks for "library_b:RELEASE" and is unable find it, hence failing to resolve library_a.

Would be great if we can in addition to latest.* also support the maven 2 meta versions.

Start by tracing the existing handling of the latest.* metaversions in the Scala dependency-resolution code. Reproduce the reported transitive case where library_a imports library_b:RELEASE, then verify that dependencies using Maven 2 RELEASE and LATEST resolve alongside the existing latest.* behavior.

Written by the indexing model from the issue text.