fix: improve performance of config resolver

[JoshMock]

Config resolver was not parallelizing lookups, so a config with several lookups to resolve was slow as they occurred sequentially.

Also refactored the benchmark script

• output is more clear and not using a hyperfine comparative benchmark feature incorrectly
• uses a static config that does not require running any config resolvers; the benchmarks are intended to measure command schema parsing, not config lookup
• updates the baseline performance values for each script reflecting the improvements made

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	0.66s
✅ REPOSITORY	gitleaks	yes		no	no	35.87s
✅ REPOSITORY	git_diff	yes		no	no	0.4s
✅ REPOSITORY	secretlint	yes		no	no	17.17s
✅ REPOSITORY	trivy	yes		no	no	10.24s
✅ TYPESCRIPT	eslint	3		0	0	2.32s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository