GROOVY-11788: Bump JUnit to 6.0.3

[paulk-asert]

This just bumps the version but I think we need to think about whether we want a groovy-test-junit6 module.

Update: latest verison of the PR adds a groovy-test-junit6 module. I plan to discuss on mailing list.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 56 lines in your changes missing coverage. Please review.
✅ Project coverage is 66.3610%. Comparing base (e5dc35d) to head (5f7ec7b).

Files with missing lines	Patch %	Lines
...c/main/java/groovy/junit6/plugin/JUnit6Runner.java	0.0000%	44 Missing ⚠️
...roovy/junit6/plugin/GroovyJUnitRunnerHelper.groovy	0.0000%	12 Missing ⚠️

Additional details and impacted files

@@                Coverage Diff                 @@
##               master      #2412        +/-   ##
==================================================
- Coverage     66.4014%   66.3610%   -0.0404%     
+ Complexity      29893      29890         -3     
==================================================
  Files            1393       1395         +2     
  Lines          116844     116900        +56     
  Branches        20675      20686        +11     
==================================================
- Hits            77586      77576        -10     
- Misses          32892      32956        +64     
- Partials         6366       6368         +2     

Files with missing lines	Coverage Δ
...roovy/junit6/plugin/GroovyJUnitRunnerHelper.groovy	0.0000% <0.0000%> (ø)
...c/main/java/groovy/junit6/plugin/JUnit6Runner.java	0.0000% <0.0000%> (ø)

... and 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[eric-milles]

Has the API between JUnit 5 and 6 changed that much? It seems that JUnit Jupiter (covered by 5.x and 6.x) is what the groovy-test-junit5 module supports.

[paulk-asert]

@eric-milles As per the "Bumping junit jupiter to version 6" email on the dev list, this was more about maintaining a convenience for users of just having to have groovy-test-junit6 as their dependency. Also, it is flagging that there will be changes across the different Jupiter versions. For instance, Jupiter 6 supports "Native Kotlin suspend Tests". Assuming we go ahead with async/await, I wanted to see whether a similar capability for Groovy async/await made sense. If it did, targeting Jupiter 6 would seem the right target. Also, we know JUnit 3/4 is now deprecated. If it is removed in Jupiter 7, we might again want changes for a groovy-test-junit7.

Having said all that, this seems to be one of those "could go either way" type decision points. Hence the email.