Provide an editor-level warning when including output files

[DanielRosenwasser]

Something that we noticed with internal codebases, as well as even with RxJS is that tsconfig.jsons are incorrectly configured for editor scenarios and include folders like dist and lib. This means you end up with slower performance, and noisy auto-imports.

We already provide some sort of error here when compiling, but we don't provide the same error in editor scenarios.

Open questions:

• How is this information presented to the user? How is the editor given notice that it should alert a user about this?
• What exactly does it mean to include an output file? In the case of RxJS, there are no "output files" getting included in the compilation based on how we determine a file is an an output of input files. Specifically, the root-level tsconfig.json doesn't specify an outDir, so it doesn't know that it should avoid including dist. Maybe we can use some directory-naming heuristics when we find one folder named src and another named dist or lib?

[DanielRosenwasser]

@mjbvz @amcasey you might be interested in this

[DanielRosenwasser]

Related is @andrewbranch's #39267

[mjbvz]

Seems useful.

For this first point, TS already generates config file diagnostics. This seems like it would fall under that