Support programmatic registration of resource locks

[vdmitrienko]

Solves: #2677

Overview

Introduce adding shared resources programmatically via @ResourceLock(providers = ...) attribute
which accepts an array of one or more classes implementing ResourceLocksProvider interface.

It allows to add resources in runtime (immediately before starting execution on the engine level).

Resources can be distributed based on any test class / nested test class / test method attributes (e.g. package name, class / method name etc.) or any other user logic.

This approach serves as a more flexible and less verbose alternative for cases in which:

• adding lots of @ResourceLock(value, mode) annotations manually may be inconvenient;
• shared resources are not known until runtime.

---

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
• Change is documented in the Release Notes

[marcphilipp]

Looks very promising! Sorry for the late request to change the API.

[vdmitrienko]

Hi @marcphilipp
Maybe you have any updates regarding this PR?

[vdmitrienko]

Thanks! I'll take it from here.

Thank you!
This was my first contribution, and it was very interesting and valuable experience.