Replacing @Theory annotated test case to @Parameterized test case

[joviegas]

Motivation and Context

• Removing @theory annotated test cases since that annotation is experimental. This was causing integ test case to be stuck while test were getting loaded.
• Also reverting the temp fix done as part of PR#2984

Modifications

• Added timeout to detect any deadlocks.
• Added Parameterized test case.

Testing

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

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

[cenedhryn]

Nice way of providing the combinations. How about

    private static Stream<Arguments> permutationsOfCrtCallParameters() {
        return Arrays.stream(eventLoopValues).flatMap(
            eventLoops -> Arrays.stream(connectionsValues).flatMap(
                connections -> Arrays.stream(requestValues).flatMap(
                    requests -> Arrays.stream(parallelClientValues).flatMap(
                        parallelClients -> Arrays.stream(sharedClientValue).map(
                            sharedClients -> Arguments.of(eventLoops, connections, requests, parallelClients, sharedClients))))));
    }

Including the parameter names instead of s1 etc makes it less abstract, and also collecting the parenthesis at the end is easier to read

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication