Fix Windows CI with jest as alternative to bun, also add more matrix envs

[fritx]

Goal:
Add and fix CI for Windows

Problem:
bun is not availble in Windows currently (ref: oven-sh/bun#8045, oven-sh/bun#7991).
Tried with both setup-bun (docs, failed) and powershell -c "irm bun.sh/install.ps1|iex" (docs, failed)

Solution:
For Windows, switching to npm install + jest as alternative to bun install + bun test.

Details:

• Completing the CI matrix.envs: ubuntu-bun, ubuntu-jest, macos-bun, macos-jest, windows-jest
• Making tests compatible with node + jest:
  • replacing toInclude => toContain
  • adding some missing is_browser detections
  • skipping esbuild: false test (bun only)
  • introducing es-main to detect and prevent unexpected call of getArgs (throwing on the wrong args)
• Making tests compatible with Windows:
  • introducing toMatchOSPath
  • handling some paths with path.normalize or (path/posix).join

✅ The CI are all passing:
https://github.com/nuejs/nue/actions/runs/7463368446

[nobkd]

Just an idea... should we use the lock-file(s) for dependency installation?
That might make the test-runs more reproducible.
Referring to #150 (comment)

I mean... the test / build library might still change (new line 25 / 33), but at least the main dependencies would be the same

I'm not sure if it's a great idea, but it came to my mind.

[fritx]

Yes. It's a good question. I'm +1. For each project, we have different choices. Like:

• simple: totally ignoring all the lock-files
• sample: ...or just keeping one of the lock-files as a sample, e.g., yarn.lock (via bun-install -y)
• strict: ...or even keeping all the lock-files (bun, yarn, pnpm, npm, etc)

IMO, I personally prefer the choice 1 or 2, as nuejs is a quite lightweight framework or tool. Keeping more than 1 lock-files can be much effort while committing and code-reviewing. (which means to remove most of the lock-files and add them into .gitignore)

How do you guys think? @nobkd

[fritx]

Sorry. Closing for some cleaning work. Would re-open later...