Use NodeNext for Typescript module resolution

[akphi]

Fixes #486

@nene This is an extensive fix to upgrade the codebase to fully embrace ESM (i.e. specifying extensions in exports). This will make sql-formatter naturally work with Typescript projects which use module = Node16/NodeNext. Otherwise, we will have to find some other way to tweak package.json to make things work.

For example, uuid

https://github.com/uuidjs/uuid/blob/main/package.json

doesn't use the field type: module and fully specify exports but I personally think it's just makeshift, we might as well move to adopt ESM fully.

---

I have run yarn build and yarn test locally to make sure things work.
One thing you might not like is I don't think we could use alias like src anymore so I resolved all imports to use relative paths, sorry about that 🙏

[nene]

Thanks for the bug report and pull request.

It turns out that the ts-transform-paths plugin doesn't work with latest TypeScript. It should be compiling away these src/ paths, but it's not working. I tried applying some of the suggested patches, but they also did nothing. Given that this issue has remained unsolved for about a year, it's probably better to move away from using of that plugin.

[nene]

These fixes, plus a few more, are now released as 11.0.1

[akphi]

These fixes, plus a few more, are now released as 11.0.1

Fantastic! Thank you so much!