chore: local support for node --strip-types

[SuperchupuDev]

Note

This PR doesn't affect the published dist code nor any file that's published to npm whatsoever. Its only purpose is to improve the experience of working with fdir's typescript source code, for people who clone the repo to contribute to it.

Currently, whenever you want to locally do a small test on fdir (to see if the code is working etc), you have to rebuild each time you change the source code, unless you use something like ts-node. This works, but it's far from ideal.

Now that important PRs are merged, I'm proposing a small change that would greatly improve DX for anyone contributing to this project. Months ago, node released support for natively running typescript code, but it requires the code to specify type imports, do not make use of any non-erasable syntax (such as enums) and specify the .ts extension when importing typescript files.

This PR makes the necessary changes to the source code to allow you to allow you to import fdir's typescript files directly in node:

// a.ts
import { fdir } from "./src/index.ts";
const api = new fdir()
  .withFullPaths()
  .crawl('.');

const result = await api.withPromise();
console.log(result.length);

$ node a.ts
7100

This PR doesn't remove support for anything, all tools still work fine, like ts-node or vitest

It also prevents tsc from emitting any code, since we're supposed to build with tsdown now, removes the forceConsistentCasingInFileNames config option (since it's on by default) and adds a typecheck workflow (the test workflow never did any typechecking) with dependency caching to significantly reduce CI times.

I haven't removed ts-node from the dev dependencies since you still might want to use it when benchmarking on node versions that don't have --strip-types.

This PR affects many files and I'd completely understand if it doesn't get accepted. It would just really improve the experience of contributing to fdir.