Reduce false negative cases of typescript parser tests

[JLHwung]

Q	A
Fixed Issues?	Reduced the false positive cases of parser-typescript-tests
License	MIT

For details please refer to the comment section of new files.

I have commented out the error codes which would introduce new false positive cases, so that this PR is only removing the false negative cases.

Before

 ✔ 4293 valid programs parsed without error
 ✔ 277 invalid programs produced a parsing error
 ✔ 4 invalid programs did not produce a parsing error (and allowed by the whitelist file)
 ✔ 505 valid programs produced a parsing error (and allowed by the whitelist file)

After

 ✔ 4293 valid programs parsed without error
 ✔ 388 invalid programs produced a parsing error
 ✔ 4 invalid programs did not produce a parsing error (and allowed by the whitelist file)
 ✔ 395 valid programs produced a parsing error (and allowed by the whitelist file)

When reading the TypeScript tests, I realize that some false negative cases comes from that we are not running test properly. i.e. declarationMapsOutFile.ts uses @filename annotation to specify multiple typescript files inside a single testcase. But we are parsing the whole testcase a single file, this would introduce FN especially if the case is testing import/exports. That's why we have many import/export related case in the whitelists. I would address this issue in a separate PR.

[JLHwung]

Use the bundled typescript bin since the dev dependency could be out-of-dated.

[JLHwung]

TypeScript does not push parseDiagnostics for all and not limited to these errors. 🤷

[nicolo-ribaudo]

Thanks!