chore: hoist node.js bindings on top of rust sdk

[tychoish]

The commit history is wacky because I started this work before the SDK branch was fully merged but the diff is normal.

@greyscaled if you wanna take this for a spin, that'd be cool too.

[universalmind303]

we should probably just return a new instance each time. This seems like it could produce some unexpected behavior.

such as.

const db1 = glaredb.connect() 

const db2 = glaredb.connect() 

I'd expect these to be two separate sessions, but this code looks like they'd use a shared connection.

JS isn't really known for it's performance, so the cost of spinning up a new session is likely not a concern. It's what we are already doing, and seems a bit safer a

[tychoish]

I'd expect these to be two separate sessions, but this code looks like they'd use a shared connection.

This is complicated:

• before 138347b, there was only one glaredb in memory database (particularly confusing for testing, I think, but also users.)
• as of chore: integrate new rust sdk into python bindings #2850, the python driver has (will have) the semantics you (and I) expect, as above.
• also as of that PR the glaredb.sql() and glaredb.execute() functions in python, will access this static/global shared db.
• I believe, that we could have a similar (global) functionality in node, but I'd be happy to drop it. my grep shows that this is never called.

[tychoish]

So this patch mirrors the Python PR, which has a few quirks in service of making it possible to reference python variables as tables in later SQL queries (which means that the result of the sql() and prql() methods need to be re-executable.)

Most of the quirks of this implementation are in service of mirroring the python implementation, but I think if we don't intend to have this API, then we can have a much simpler implementation here.