Performance degrades the more wildcards that are contained in TSConfig include or exclude patterns

Nobody has claimed this yet.

### 🔎 Search Terms

wildcard pattern include exclude tsconfig regex regexp regular expression glob performance slow node

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

_No response_

### 💻 Code

Create a TS project with any empty TS file and the following TSConfig.
```json
{
"compilerOptions": {
"noCheck": true,
"noEmit": true,
"noResolve": true,
},
"exclude": [
"alpha/beta/gamma/delta/epsilon/zeta/eta/theta/iota/kappa/lambda/**/*.ts",
"alpha/beta/gamma/delta/epsilon/zeta/eta/theta/iota/kappa/lambda/**/*.ts",
"alpha/beta/gamma/delta/epsilon/zeta/eta/theta/iota/kappa/lambda/**/*.ts",
...repeat a couple hundred or more times
]
}
```
I've created a repo to more easily reproduce the behavior: https://github.com/MichaelMitchell-at/typescript_slow_wildcards_repro

### 🙁 Actual behavior

`tsc` takes several seconds to run on the project, even though there is no work to do and there are no files to compare the `exclude` patterns against. In fact, running `tsc` with `node --jitless` is much faster than without.

### 🙂 Expected behavior

`tsc` should complete quickly.

### Additional information about the issue

I've determined through profiling that the issue is that a giant `RegExp` combining all the patterns gets created which is very slow to evaluate.
https://github.com/microsoft/TypeScript/blob/739d729ecce60771c23723aad932ab35a34df82d/src/compiler/utilities.ts#L9556-L9566

From my testing, it's much faster to build a separate `RegExp` for each pattern and test them one by one for large number of patterns and for a small number of patterns there is no perceivable difference in speed. I've created a PR implementing this change which greatly improves the performance: https://github.com/microsoft/TypeScript/pull/61104

Start in src/compiler/utilities.ts at lines 9556-9566, then run the linked typescript_slow_wildcards_repro project with the repeated tsconfig exclude patterns. Compare the compiler runtime for large and small pattern sets, and consider the existing PR 61104 when verifying the expected performance improvement.

Written by the indexing model from the issue text.