Make .js paths lookup for .ts as a 2nd fallback

[izelnakri]

Currently doesnt work on typescript projects that has the relative files referenced as with ".js". This behavior must be included in this package. Example:

import Changeset from "./changeset.js"; // clicking on gf should go to ./changeset.ts
import RevisionHistory from "./revision-history.ts";
import Serializer, { transformValue } from "./serializer.js";

console.log(Changeset, RevisionHistory, Serializer, transformValue);

This is actually an unfortunate best practice decided by the typescript team, they are on purpose not changing typescript compiler behavior for years and advocate for the use of .js extensions for projects that build/transpile for node.js ESM imports. In order to build a typescript file that typechecks, transpiles correctly to ES module it is expected to be referenced as "./module.js" even if the file is actually a "./module.ts".

Related references:
microsoft/TypeScript#16577 (comment) <- The relevant github issue
https://stackoverflow.com/questions/62619058/appending-js-extension-on-relative-import-statements-during-typescript-compilat/62626938#62626938