chore: hardcoded configuration values should be centralized #4902
Description
Description
Performance and configuration values are scattered across the codebase without clear rationale:
GitHubReporter.cs:21—MaxFileSizeInBytes = 1 * 1024 * 1024(1MB)TestBuilderPipeline.cs:25—MinItemsForParallel = 8- Various parallelization thresholds in
TestScheduler.cs
No way to tune these without code changes.
Suggested Fix
Centralize into TUnit.Engine/Configuration/PerformanceConstants.cs with documented rationale for each chosen value.