Add explicit exclude and include paths to tsconfig

[huntie]

Summary:

Intends to resolve #129.

See https://github.com/microsoft/Typescript/wiki/Performance#configuring-tsconfigjson-or-jsconfigjson recommendations.

Changelog:

[GENERAL][CHANGED] - Scope include paths in tsconfig.json

Test Plan:

Comparison:

[kraenhansen]

Perhaps we would want to include (or actually move) the **/Pods/** from the config being extended? https://github.com/facebook/react-native/blob/ca764bb5115d2e7baa6e07c49e64d4806f5b3d4a/packages/typescript-config/tsconfig.json#L41

[huntie]

@kraenhansen Wouldn't hurt — added. Probably best to leave in the base config for a while (existing projects).

[kraenhansen]

@huntie I actually don't think it's effective (based on the description and issue linked from facebook/react-native#42375) and I have a suspicion that facebook/react-native#42909 was never tested 🙈

[huntie]

@kraenhansen Hmm, good notes.

On an empty template:

• *.ts, *.tsx — Significant, avoids over-including config files and resolving their dependencies.
• **/node_modules — Useful in case of any conversion to a monorepo (TS will only ignore a root node_modules dir by default).
• **/Pods — Useful once pods are installed, if they contain TS sources.

And it looks like tsc reaches into node_modules regardless, but only if depended on by the input program. As such, I'm not super sure we're solving the perf issue reported — unless this involved a monorepo setup (moderately likely!).

Test plan updated.