fix: tsconfig validator fails on chained tsconfig references

[bduffany]

Fixes an issue (#2513) that the validator was always treating extends as a plain old file instead of reading TsConfigInfo to get transitive deps. See the added test case, which shows a realistic example that would fail to validate due to missing tsconfig.base.json (referenced by tsconfig.node.json, which itself is referenced by main/tsconfig.json)

(Note: one workaround in case anyone stumbles upon this PR is to use validate = False).

[alexeagle]

Thanks for the help, do you think you'll be able to get the tests green?

[bduffany]

Fixed most of the failing tests. There's a few that are still failing (on Windows only).

• windows failure looks like an issue with compiling @types/jasmine and @types/jest, which seems unrelated.
• windows_examples failure is error TS5033: Could not write file 'bazel-out/x64_windows-fastbuild/bin/car.spec.js': EPERM: operation not permitted, open 'bazel-out/x64_windows-fastbuild/bin/car.spec.js'. Seems unrelated to this PR.

[bduffany]

Friendly ping -- would it be possible to re-run the Windows tests to see whether the failures are specific to this PR?

[alexeagle]

Hey sorry for the delay, juggling lots of things lately. You can always come ping me on slack if we're mostly done with a PR and a bit of attention is needed.

Yes those windows failures are legit. Actually they are failures in non-sandboxed mode, which you could reproduce on any platform, it's just that Windows is always in that mode.

What's happening is the typescript compiler does it's implicit look-around-the-disk to find ambient typings it can add to the program. When it does this, it finds typings we don't want to be included, they introduce conflicts with other typings. This is why we have types: [] in most tsconfig's to disable this feature and we are explicit about the typings we want in each compile.

[google-cla]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[alexeagle]

@googlebot I consent.

[alexeagle]

thanks!

[bduffany]

@alexeagle Thanks for finishing this off!