Revise stack trace pruning

[juliette-derancourt]

Context

Stack trace pruning was introduced in #3247.
We want this feature to be disabled for tests inside this repository (otherwise all stack traces would be almost empty), and it is when the tests are launched via gradle (due to this setting). But when launched in a different way, this setting have no impact and the feature is therefore enabled when it shouldn’t.

Solution

A potential solution could be to not prune stack traces of tests specifically located inside the org.junit package, even when the feature is enabled.

Related

• Prune stack traces produced by failing tests #3277 (comment)

Deliverables

• Collect MethodSource and ClassSource instances from the current test descriptor and its parents, find the bottom-most stackframe with one of these classes, and include all stackframe upward from there
• Don't prune everything from java.* and jdk.*, just the reflection packages from both but only below the test method
• Remove package pattern configuration parameter introduced in M1