The idea is to let caller be able to augment the nature of metadata to resolve version range from.

Resolver already handles this, and is more elegant, than to have caller fiddle with
filtering the remote repositories or alike. Also, this way client code (ie. Maven)
can expose more fine grained configuration for this.

self-assigned this

cstamas marked this pull request as ready for review

cstamas added a commit to cstamas/maven that referenced this pull request

Ability to control which repositories to be queried to resolve
ranges. Introduced new property:

`maven.versionRangeResolutionNature` that is used in VersionRangeResolver,
and mean:
* not set; behave as before (default)
* "auto" string; will check lower and upper bounds, and if any is snapshot, will querty snapshot reposes otherwise not
* any valid value of resolver Metadata.Nature enum; then will use that

Depends on apache/maven-resolver#1518