Introduce method filter support in the ConsoleLauncher

[yhkuo41]

Issue: #3107

Overview

Solves #3107.

After referring to other Filters (such as TagFilter), I am not sure if I should implement both IncludeMethodFilter and ExcludeMethodFilter, please let me know if I should remove IncludeMethodFilter.

---

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 and Release Notes
• All continuous integration builds pass

[marcphilipp]

After referring to other Filters (such as TagFilter), I am not sure if I should implement both IncludeMethodFilter and ExcludeMethodFilter, please let me know if I should remove IncludeMethodFilter.

We originally thought we didn't need an include filter because there's already a way to select particular methods. However, the latter does not allow specifying wildcards so there might be some use cases where it would be beneficial.

Team decision: Add both --include-methodname and --exclude-methodname.

[yhkuo41]

@marcphilipp Thanks for the feedback, I've added the cli options.

[marcphilipp]

I'm afraid I caused a lot of merge conflicts by introducing subcommands in the ConsoleLauncher recently. The new options should now be added to TestDiscoveryOptionsMixin.FilterOptions instead.

@Sakieye Do you have time to rework the PR?

[yhkuo41]

I'm afraid I caused a lot of merge conflicts by introducing subcommands in the ConsoleLauncher recently. The new options should now be added to TestDiscoveryOptionsMixin.FilterOptions instead.

@Sakieye Do you have time to rework the PR?

@marcphilipp I've updated my PR, please help review again