feat(analyze): Replace wasm-bindgen with jco generated bindings

[blaine-arcjet]

This replaces our wasm-bindgen generated code with jco generated code. Switching to jco aligns us with our desire to use the WebAssembly Component Model throughout our codebase. Through the Component Model, we can define concrete types in a wit file, like our bot-type enum:

enum bot-type {
    unspecified,
    not-analyzed,
    automated,
    likely-automated,
    likely-not-a-bot,
    verified-bot,
}

This allows us to have one definition and do minimal-to-no translation. This will also allow us to eventually do away with JSON.stringify and JSON.parse on inputs/outputs on the Wasm boundary.

Additionally, the --instantiation mode of jco allows us to do away with our custom wasm instantiation.

Since jco is used to produce various wasm "core" modules, I've moved the base64 module generation into a Rollup plugin in the analyze package. Any time a .wasm import (but not a .wasm?module import) is encountered during the build, it is translated into a virtual module and the base64 version is produced during the load phase.

[trunk-io]

😎 Merged successfully - details.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@bytecodealliance/[email protected]	Transitive: environment, eval, filesystem, shell	+33	36.2 MB	guybedford

🚮 Removed packages: npm/@arcjet/[email protected], npm/@arcjet/[email protected], npm/@arcjet/[email protected], npm/@types/[email protected], npm/@types/[email protected]

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[blaine-arcjet]

@SocketSecurity ignore npm/[email protected]