upgrade typescript, add ts_project angular test

[jbedard]

I wanted to test a modern version of angular which includes angular/angular#36290, that requires a modern version of typescript. I can move that to a separate PR if wanted.

Main goal was adding a ts_project(tsc=ngc) test. When enabling workers something goes wrong, it seems like ngc is no longer used and it uses tsc in the worker. That will be next... either a bug fix or disable workers if a custom tsc is passed in as a quick solution?

[jbedard]

This is the only file where the diff seems odd 🤔

getDefaultExportFromCjs is a rollup method, not typescript... why would a typescript update cause this?

and some of this just looks odd, like doing the defineProperty(exports, "__esModule" twice 🤔

[alexeagle]

I think it's possible and reasonable that rollup does something different when it sees the changed output from TypeScript that resulted from microsoft/TypeScript#37093

Like there is now a default export from this file and wasn't before? https://github.com/bazelbuild/rules_nodejs/blob/stable/packages/runfiles/index.ts

[alexeagle]

aeagle@aeagle-a01 rules_nodejs % diff dist/bin/packages/runfiles/index.js /tmp/index.js
2a3
> exports.runfiles = exports._BAZEL_OUT_REGEX = exports.Runfiles = void 0;
4c5
< exports.Runfiles = runfiles_1.Runfiles;
---
> Object.defineProperty(exports, "Runfiles", { enumerable: true, get: function () { return runfiles_1.Runfiles; } });
6c7
< exports._BAZEL_OUT_REGEX = paths_1.BAZEL_OUT_REGEX;
---
> Object.defineProperty(exports, "_BAZEL_OUT_REGEX", { enumerable: true, get: function () { return paths_1.BAZEL_OUT_REGEX; } });

[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.

[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.

[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.