[MNG-7409] Improve exception message for VersionResolutionException thrown from o.a.m.repository.internal.DefaultVersionResolver

**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[MNG-7409](https://issues.apache.org/jira/browse/MNG-7409?redirect=false)** and commented

I have seen the following exception message with Maven 3.8.4

```
[DEBUG] Skipped remote request for com.adobe.aem:aemanalyser-maven-plugin/maven-metadata.xml locally installed metadata up-to-date
....
[ERROR]
Caused by: org.eclipse.aether.resolution.VersionResolutionException: Failed to resolve version for com.adobe.aem:aemanalyser-maven-plugin:jar:RELEASE
at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion (DefaultVersionResolver.java:276)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveVersion (DefaultRepositorySystem.java:240)
at com.adobe.aem.analyser.mojos.VersionUtil.getLatestVersion (VersionUtil.java:232)
at com.adobe.aem.analyser.mojos.VersionUtil.checkPluginVersion (VersionUtil.java:253)
at com.adobe.aem.analyser.mojos.AemAnalyseMojo.execute (AemAnalyseMojo.java:243)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
```

(this was triggered in https://github.com/adobe/aemanalyser-maven-plugin/issues/138).
The real cause is not visible in the stack trace as it seems that the `VersionResult` being passed to the constructor of `VersionResolutionException` in https://github.com/apache/maven/blob/6ca13af230e9a7c6dcb0bf629d9a2676d8f833ed/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionResolver.java#L242 does not contain enough information.

---

**Affects:** 3.8.4