feat(builtin): add basic ESM support

[Toxicable]

PR Checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Feature (please, look at the "Scope of the project" section in the README.md file)

What is the current behavior?

Issue Number: #3277

What is the new behavior?

Adds ESM support in for nodejs_binary, jasmine_node_test and ts_project

Does this PR introduce a breaking change?

• No - Only changes are internal API's

[Toxicable]

Things to note:

• requires typescript > 4.5
• requires jasmine > 3.7
• Editor support requires a manual file association for *.mts -> typescript
• Imports are required to end with .mjs and there's not currently editor support (ticket likely exists needs to be found or created)
• Typescript reference https://www.typescriptlang.org/docs/handbook/esm-node.html

[Toxicable]

I've extracted ts_project support into a seperate MR #3298

[Toxicable]

CI looks mostly green now
Aside from this failure, which looks like it's unrelated and only on windows

ERROR: C:/b/bk-windows-zzbr/bazel/rules-nodejs-nodejs/internal/node/test/chdir/BUILD.bazel:20:16: output 'internal/node/test/chdir/package.json' was not created

[devversion]

This looks great to me.

[devversion]

Is this intentionally part of this PR?

[Toxicable]

Ah, this change isn't related to this PR, but I needed it so that yarn wouldn't try pull packages from another registry that I have configured.
I don't think anyone else would have this issue, but it wouldn't cause an issue leaving it in as well.
Happy to remove if you think so

[devversion]

No problem with me, just asked since it seemed unrelated 😄