Components: Invert tsconfig to be exclude-based

[mirka]

Related to #35744

What?

Changes the tsconfig for the components package so that it is an exclude list rather than an include list.

Why?

Currently the TypeScript data for the components package is not available outside the package itself, because we do not generate an index.d.ts in the build-types folder. To do this, we need to get to a point where src/index.js can be included in our tsconfig.json. This is a good milestone to hit in the process of working on #35744.

We don't necessarily need to manually convert all the remaining components in #35744 before we can hit this milestone, because as long as everything in the code path of src/index.js is free of TS errors, it will build. They can still be .js files, or they can be @ts-nochecked.

With this in mind, I think this is a good time to flip the tsconfig so it is an exclude list instead of an include list.

Benefits

• All new files (outside of excluded paths) will be checked by default.
• It immediately adds typechecking to some non-erroring paths that weren't in the include list yet.
• It makes it easier to see what paths are left before we can reach our src/index.js milestone.

How?

Starting with a universal include, I ran npx tsc --build --watch and added excludes for paths that were erroring. Then, I made sure that all paths in the former include list were still included.

Testing Instructions

✅ The types still build

[ciampo]

cc'ing @sirreal in case he has any wisdom to sprinkle — do you see any issues with this approach?

[ciampo]

LGTM 🚀

Code changes look good, and I checked on my machine that the build, build-module, build-style and build-types directories have the exact same contents before and after the tsconfig.json changes