Fix loading react-jsxdev instead of react-jsx

[Jarred-Sumner]

What does this PR do?

Fixes #3768

Fix loading react-jsxdev instead of react-jsx

The main bug: the state of the resolver sometimes got out of sync with the state of the transpiler for tracking if it should use development JSX or non-development JSX. This meant that setting NODE_ENV to a value in the parent process that is different than the environment seen from Bun.build would cause this to not work properly.

Separately, I also implemented tracking react-jsx and react-jsxdev to work as expected.

How did you verify your code works?

There is a test that runs each permutation of NODE_ENV for runtime and bundler.

There is also a test for Bun.serve() static

[robobun]

^{Updated 2:07 PM PT - Feb 3rd, 2025}

❌ @paperclover, your commit 523bf96 has 1 failures in Build #11064:

• test/js/node/test/parallel/test-fs-promises-writefile.js - code 1 on 🪟 2019 x64-baseline

---

🧪   try this PR locally:

bunx bun-pr 17013

[paperclover]

review comments addressed in person. i will probably fix these last points

• convert ?bool into an enum tristate between unspecified, production, development
• document the behavior