feat(resolver): Add NODE_PATH support

[AielloChan]

What does this PR do?

Add resolve check for NODE_PATH.

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

I wrote automated tests

• I included a test for the new code, or existing tests cover it

• I ran my tests locally and they pass (bun-debug test test-file-name.test)

• I checked the lifetime of memory allocated to verify it's (1) freed and (2) only freed when it should be

• I included a test for the new code, or an existing test covers it

• JSValue used outside outside of the stack is either wrapped in a JSC.Strong or is JSValueProtect'ed

• I wrote TypeScript/JavaScript tests and they pass locally (bun-debug test test-file-name.test)

[AielloChan]

#13125

[paperdave]

tiny nitpick but this looks incredibly reasonable

can you add a test that checks that more than one NODE_PATH entries work?

[paperdave]

couldn't this just be const node_path = and then moving the second if check inside of this one?

[AielloChan]

All done

[AielloChan]

@paperdave Looks some github action configure was broken. Runner image is Ubuntu, but script try to call a zig.exe

/usr/bin/bash: line 1: vendor/zig/zig.exe: No such file or directory
error: script "zig" exited with code 127
error: script "zig:fmt" exited with code 127
error: script "fmt:zig" exited with code [12](https://github.com/oven-sh/bun/actions/runs/11006290644/job/30561806366?pr=14089#step:7:13)7
Error: Process completed with exit code 127.

[bingtsingw]

@paperdave Hi, is this pr ready to be merged?