Document parameter resolution conflicts

[jabhatfield]

Issue: #1190

Overview

User guide updated to explain ParameterResolver conflicts and provide some ways to resolve them.

---

I hereby agree to the terms of the JUnit Contributor License Agreement.

---

Definition of Done

• There are no TODOs left in the code
• Method preconditions are checked and documented in the method's Javadoc
• Coding conventions (e.g. for logging) have been followed
• Change is covered by automated tests including corner cases, errors, and exception handling
• Public API has Javadoc and @API annotations
• Change is documented in the User Guide and Release Notes

[jabhatfield]

Please could I get some feedback for this PR?

[marcphilipp]

Sorry for the delay! The new section does a good job at explaining why/when conflicts occur. However, it does not document the best practices mentioned in the issue description. For example, using a custom annotation and/or a custom parameter type. Could you please add that?

[marcphilipp]

Suggested change

	declared within a test class, a `ParameterResolutionException` will be thrown, with a
	registered for a test, a `ParameterResolutionException` will be thrown, with a

[jabhatfield]

Wording updated

[marcphilipp]

Suggested change

	message to indicate that competing types have been discovered. See the following example:
	message to indicate that competing resolvers have been discovered. See the following example:

[jabhatfield]

Wording updated

[marcphilipp]

Using @ExtendWith would be more idiomatic here and below because there's no state or configuration that would justify programmatic extension registration.

[jabhatfield]

Changed to @ExtendWith here and also in the other code examples.

[jabhatfield]

Sorry for the delay! The new section does a good job at explaining why/when conflicts occur. However, it does not document the best practices mentioned in the issue description. For example, using a custom annotation and/or a custom parameter type. Could you please add that?

Thanks for the feedback! I've added examples of using a custom type and a custom annotation.