JupiterTestEngine attempts to resolve unique IDs that belong to other engines

[sbrannen]

Overview

Currently, the JupiterTestEngine needlessly attempts to resolve Unique IDs that clearly belong to other test engines. This is because JavaElementsResolver.resolveUniqueId(UniqueId) completely ignores the Engine ID and then blindly attempts to resolve the supplied Unique ID. Consequently, the JupiterTestEngine always logs a warning about not being able to resolve a Unique ID that it was never meant to resolve.

Related Issues

• Cannot select @TestTemplate or @TestFactory invocations by Unique ID #1025

Deliverables

• Ensure that the JupiterTestEngine does not attempt to resolve Unique IDs that belong to other test engines.