Create new declaration file for native build

[querolita]

Right now, the type declarations for TS live in plonk_wasm.d.ts. Despite having overwritten in node_backend.js the FFIs and types that have been reimplemented with napi on Rust , TS is still expecting those types to have a WASM-like shape (contains pointers, etc). This forces us to ab-use any and unknown in the native conversion layer. In runtime, the objects that TS will receive will indeed have the napi shape (thanks to the conversion bundle switch between wasm and napi), but at compile time they are still expected to be WASMs.

When all of this is in place, we should regenerate the type definitions napi build --dts to produce an equivalent plonk_napi.d.ts, so that the conversion layer can be correctly typed.

[querolita]

Config flag for dtsHeader

Enable jsBindings

[bleepbloopsify]

I did an investigation on this:

https://github.com/o1-labs/o1js/pull/2591/files
o1-labs/proof-systems#3350

(mina PR just bumps proof-systems)

napi-rs/cli expects us to export the native bundle as a solitary npm package, rather than just handing us the type declarations in a nice typescript interface.

We could:

1. fork napi-rs/cli, and hook into the typegen ourselves, and make it do things that we like. (This might be the most stable)
2. set it up so we generate an entire local package.json to isolate the plonk-napi package (I did a poc on this bleepbloopsify/npm-poc@69a9449)
3. Write the typescript types ourselves (I hate this option, please don't do this, this might be VERY bad)

Option 2 is a nice, viable option at the moment, but we need to be very explicit about what architecture we're supporting. @querolita do we have a list of "target architectures" we need to support somewhere?

[bleepbloopsify]

#2415

I found the list