feat: explicit loading of native binaries

[belgattitude]

Proposal to fix: #126

Before this change, the loading of node js binary was fully dynamic.

The proposed way to do this is to explicitly define all binaries that could be loaded. That helps framework that applies tracing on node_modules such as nextjs (when deployed as lambda or standalone) to detect that the binary is in use. It also allows to set a custom message indicating the reason of error.

• Is the proposed way good enough ?
• What error message to display when an architecture isn't supported ?

There's many other ways to achieve the same idea (see esbuild, or sharp with require.resolve), this one keeps the loading as simple possible.

Happy to discuss if it makes sense

[jraymakers]

A few minor questions/comments about the code patterns. The overall approach makes sense.

[belgattitude]

@jraymakers I've updated the PR. Didn't went to the nested switch though :)

Hope it can get merged soon, I'm really excited by duckdb neo so far.

[jraymakers]

This can probably be simplified further (I suspect the function wrapping the string interpolation, and the later string split, are not necessary), but it should work fine as-is. Thanks for the contribution!