Remove sorting parameter from ConfigurationSessionTestSuite #903

[HeikoKlare]

The ConfigurationSessionTestSuite sorts the test methods by default. A field identifies whether sorting is activated, but the field cannot even be set but is always true. So, this parameterization is completely obsolete and only introduces unnecessary complexity to the session test framework.

This unnecessary complexity in the JUnit 3 implementation of session tests complicates their migration to JUnit 5. I propose to incrementally remove all unused functionality from the JUnit 3 session test implementation while migrating the actual test classes to the JUnit 5 equivalent and incrementally enhancing the JUnit 5 implementation with what is required. This applies one step of that incremental removal of unused functionality in the JUnit 3 implementation of session tests.

Contributes to https://github.com/eclipse-platform/eclipse.platform/issues/903

❗This removal becomes particularly useful when also #1354 removing shared session support is applied, as in combination even more code can be removed due to conditions becoming empty.

[github-actions[bot]]

Test Results

 1 734 files  ±0   1 734 suites  ±0   1h 21m 56s :stopwatch: - 3m 53s  3 972 tests ±0   3 950 :white_check_mark: ±0   22 :zzz: ±0  0 :x: ±0  12 513 runs  ±0  12 352 :white_check_mark: ±0  161 :zzz: ±0  0 :x: ±0 

Results for commit 969aac6a. ± Comparison against base commit 29d6edfa.

:recycle: This comment has been updated with latest results.