Migrate most tests to JUnit 5

[Bennett-Lynch]

JUnit 4 -> 5 migrations are often done in a 3-step process:

1. Update dependencies to JUnit 5, including the vintage module, causing all tests to leverage the new JUnit 5 Platform (completed in [JUnit 5] Migrate to JUnit 5 Platform (with existing JUnit 4 test cases) #2850)
2. Incrementally migrate JUnit 4 tests to JUnit 5 tests
3. Once no JUnit 4 usage remains, remove the dependency on the vintage module

This PR begins step 2 by migrating tests which can be easily converted.

This PR excludes JUnit 4 tests which leverage any of the following:

1. The expected parameter in test annotations
2. The timeout parameter in test annotations
3. The class-level @RunWith annotation (e.g., @RunWith(Parameterized.class) and @RunWith(MockitoJUnitRunner.class))
4. Or if the test has child/parent classes that cannot be updated in a consistent fashion

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2969 Code Smells

No Coverage information
0.0% Duplication

[dagnir]

Please ensure the JDK8 build job is passing before merging