ci: Cleanup and enforce types check

[mattrunyon]

Was going through actions to figure out where to add docs PR previews and saw this type check action was not part of the enforced tests, missing setup-node (so not sure what version it was using), and adding functionality that setup-node already provides (matchers for tsc and eslint errors in logs).

I added JS build to the test-js-packages step. This isn't completely necessary since the e2e job should fail if the packages fail to build, but figured an explicit check was good to add.

[bmingles]

@mattrunyon Was this left here intentionally?

[mattrunyon]

Yes I did it to test that the CI test actually fails. Turns out I broke CI because it runs npm run build -- --scope <plugin> and I changed the build script at the root. I'll fix that

[mattrunyon]

This is what I wanted to see which was what the Python file was doing before. It's built-in to the setup-node action.

[bmingles]

Left a couple of comments

[mattrunyon]

I also added fail-fast: false to our matrix testing. I can move that to a separate PR if you want. It just makes it easier to see what the errors are because a bunch of in-progress jobs would get stopped with the default fal-fast: true. So it made it hard to determine if it's a Python version-specific issue, general Python issue, etc. This way the tests will run for all versions in the matrix regardless of the outcome of the others.

[bmingles]

LGTM