[SUREFIRE-2051] Propagate exceptions while resolving artifacts in SurefireDependencyResolver

[hisener]

Surefire doesn't propagate the exception during artifact resolution, and then later, it fails with a NullPointerException when it needs to access the artifact (in AbstractSurefireMojo.java#L4125 or SurefireDependencyResolver.java#L203). This makes harder to understand the underlying issue. This change uses ResolutionErrorHandler to propagate the actual issue.

---

Following this checklist to help us incorporate your
contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without
  pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles,
  where you replace SUREFIRE-XXX with the appropriate JIRA issue. Best practice
  is to use the JIRA issue title in the pull request title and in the first line of the
  commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean install to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.
• You have run the integration tests successfully (mvn -Prun-its clean install).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[Tibor17]

Right on the time!
We are about to cut the release.
Pls make requested updates.

[slawekjaranowski]

@Tibor17 I propose postpone cosmetic changes, for next PR.
After have build pass I will merge it.

[slawekjaranowski]

@hisener thanks for contribution

[Tibor17]

@Tibor17 I propose postpone cosmetic changes, for next PR. After have build pass I will merge it.

@slawekjaranowski which one?

[Tibor17]

@slawekjaranowski
Thx for taking care of the PRs #500 and #504 . Pls complete them after successful build.
I would, meanwhile build the site and I will check the page in browser if there are any visual issues. Feel free to check the site too.

[Tibor17]

@hisener
Pls squash both commits.

[hisener]

Sorry, I am seeing this just now. I'll do that. :loading: ✅

[Tibor17]

@hisener
Thx for contributing! Feel free to participate on the development in future.