The jf mvn wrapper should optimize pom version range downloads

[bedge]

When a version range is specified in a pom.xml file, eg: [2.5.0-1,2.5.0-9999)
And there are possibly 10000 poms that could match this, every one is downloaded, eg:

This can take up a huge amount of time.

Given that the jf wrapper has access to the pom.xml files, as well as the ability to

• query for the latest matching artifact versions, and
• deduce the latest version that matches the maven range,
  it could replace the range with the specific version, thereby eliminating the need to pull potentially 1000's of pom files that will neved be used.

In short,

• any maven version ranges,
• where the artifact is being pulled from a jFrog repo,
• query the repo for the latest version,
• and replace the version range string with the latest version number.

eg: Assuming a jf rf search for the artifact com.xxx.yyy.aaa, using --sort-by=created --sort-order=desc --limit=1
returns version 2.5.0-1234

replace:

        <dependency>
            <groupId>com.xxx.yyy</groupId>
            <artifactId>aaa</artifactId>
            <version>[2.5.0-1,2.5.0-9999)</version>
        </dependency>

with:

        <dependency>
            <groupId>com.xxx.yyy</groupId>
            <artifactId>aaa</artifactId>
            <version>2.5.0-1234</version>
        </dependency>

Which eliminates the need to download the pom.xml files for 2.5.0-1 - 2.5.0-1233