fix esm output

[flobacher]

simmilar to the git-adapter-github pr, this adds the extensions to relative imports.
As it feels weird and breaks direct execution of ts files, I opted to the ts extension, that tsc will change to js upon compilation due to the rewriteRelativeImportExtensions: true compiler setting.
To make the nodejs runtime aware to treat the files from the esm output dir as esm, the most minimalistic package.json with type:module is added upon build.
One final optimisation is the exclusion of tsbuildinfo files (ts incremental build cache afaik) from the published npm package. If you approve to this please add this to the git-adapter-github pr as well. Thank you very much for your awesome work on commitspark 🎉

The one usecase I found the bug with (creating migrations via the payload-cms cli that runs esm natively in nodejs without further compilation steps) works with the updated esm version. The commonjs version also still works..

[advancingu]

Thank you @flobacher !

Merged via #2

[flobacher]

Happy to contribute 🙌
When can WE expect a new package Version in npm?

[advancingu]

@flobacher New versions released for all packages.