Explore use of InvocationInterceptor to disable (parameterized) tests

In #163, I wrote:

We just updated to Jupiter 5.5 (#278) to use the new InvocationInterceptor API. If that API gets called for individual parameterized test invocations, it would be a very powerful way to implement disabling parameterized tests. The provided Invocation allows skipping tests and the ReflectiveInvocationContext seems to give access to the actual arguments. Someone should look into that and possibly create an issue if the approach seems promising. 😊

Yes, someone should.

[nipafx]

I was told I need to make an executive decision - here it is:

• parameter names: use where possible, otherwise exception with good explanation
• and/or for several annotations: or, i.e. as soon as one @DisableIf-check passes, the test is disabled
• contains and matches: disallow use of both in the same annotation for now - we can then revisit the decision later

And there’s more: We change @DisableIfDisplayName to also disallow use of both contains and matches. That change needs to be highlighted in the new documentation (including the version where that change was added.)

[Michael1993]

After wasting about an hour, I learned that while we could use Parameter#getName, it only works if the information was included during compilation (which can be checked with Parameter#isNamePresent).

I’ve created an alternate approach that’s index based. That’s always available, at least.