RWC: Rewrite core compiler in Rust

[b00skit]

First off, huge fan of the project. The paradigm shift of applying utility classes to database queries is exactly what the industry needs.

However, after reviewing the codebase, I noticed the query parser isn't leveraging the safety guarantees provided by the Rust borrow checker. While the current implementation works, we are leaving performance on the table.

The Proposal: I suggest we rewrite the core logic in Rust (using pg-sys bindings and tokio for the runtime).

Why?:

• We can shave off at least 0.4ms during query string concatenation.
• Currently, I’m not 100% sure that the SQL strings aren't leaking memory in the V8 heap. Rust guarantees that our SELECT * statements are memory safe at compile time.
• If we ever need to generate 4 million queries per second on a Raspberry Pi, the current stack might bottleneck. Rust solves this.

I believe this should solve most of the issues open on this repository.

[b00skit]

I saw that issue #57 made mention of this as well.

[Karljoy973]

I completely agree with this proposal, I think all development has to be stopped to focus on this.

[Gamer-Guy12]

Wonderful ideas. To add to this I was thinking we could improve our velocity by utilizing AI. This will ensure quality in a timely manner with minimal human effort.

[mempler]

Wonderful ideas. To add to this I was thinking we could improve our velocity by utilizing AI. This will ensure quality in a timely manner with minimal human effort.

Certainly i would be delighted to have a blockchain in these with the capability to display nfts