Allow `ParameterizedTest` annotation to receive a filter class to filter the arguments

[Llamadmiral]

We have a big codebase, and we have a lot of tests. A lot of those tests are ParameterizedTests that are connected to services that take a really long time for each test run. Unfortunately parallel test running is not really an option for us.
We had an idea to filter the ParameterizedTest arguments, however, since they can receive Enums, Fields, Classes, and Method sources, it is difficult to implement this.

My idea (which is probably not the best) is to introduce a class, that has a Stream<Arguments> filter(Stream<Arguments> arguments) method.
What we want to achieve, is to have either a round-robin, a random, or something else based run.
With this, we could run our tests with lets say, only 1 set of arguments, without touching the codebase.

Deliverables

• Have a ParameterizedTestArgumentsFilter class or interface
• Have a method Stream<Arguments> filter(Stream<Arguments> arguments)
• Use said class in the ParameterizedTests annotation.

[marcphilipp]

In addition, to Arguments, I think such a filter should also have access to ParameterDeclarations and ExtensionContext.

• Have a method Stream<Arguments> filter(Stream<Arguments> arguments)

Why would it return a Stream rather than just a boolean (similar to Predicate)?

[Llamadmiral]

I can accept ParameterDeclarations and ExtensionContext as part of the arguments.

My idea is that it would receive the stream that the ParameterizedTestExtension produces, and transform it more, hence the name "filter" might not be the best choice by me. (Maybe rename to transform or something similar)
Lets say I would want to implement a random selection logic on the ParameterizedTest, afaik that is not possible to do with Streams, because you need to do the entire chain of: Stream -> List -> select a random element -> Stream.of().
Then having just a Predicate would not suffice.