Repo (or org): add tooling to generate baselines of memory and time during linting

[JoshuaKGoldberg]

Suggestion

Every once in a while, one of us will hop onto a call with a team to try to diagnose why their type checked linting is running slowly. We'll see something like hundreds of MBs (or even a few GB) being taken up, and/or seconds-to-minutes to run. It's hard for us to give advice as to whether those measurements are normal without knowing the normal baselines for different projects:

• Files: dozens, hundreds, thousands of files?
• Structure: one project, a few project references, dozens of project references?
• Types complexity: straightforward usage, and/or many conditional types, and/or libraries such as Zod?

Proposal: let's make a dedicated package? repository? something? that can:

1. Deterministically codegen various projects across those different scales
2. Report rough space and time taken for typed linting

We'd then be able to know whether projects of similar scales are running with the expected space/time parameters.

This is really part of #6218. Maybe this issue can track a more comprehensive performance solution, while that can track the initial "get it done"?

[JoshuaKGoldberg]

@kaleidawave's JoshuaKGoldberg/dot-com#143 (comment) brings up a good idea: we could use this to showcase performance issues! I.e. all the major points in https://typescript-eslint.io/linting/troubleshooting/performance-troubleshooting could be given comparison tables showing the impact of those points. At the very least I'd love to have concrete details for eslint-plugin-import and eslint-plugin-prettier.