This should be done by wit-bindgen, but it only does it for the Rust
code generation.
https://github.com/bytecodealliance/wit-bindgen/blob/c6dc35fb6966572cae64f2720dd08cc1bcfd0f9e/crates/guest-rust/src/lib.rs#L46

This is a workaround to make sure that the constructors are called before
calling any exported functions manually.

We should use wasi-virt instead of wasi_vfs in the component model.

To share the implementation between legacy binding and the component
binding

To initialize the VM state, we have to call it before any other operation.

Fix Component support to pass `test:unit`

@bytecodealliance/preview2-shim is ESM-only package and it's hard to
maintain ESM tests with jest. So it's good time to migrate our test
suites to vitest.

 Migrate testing framework from jest to vitest

Use `bundle install --target-rbconfig` to install gems for Wasm target

Install jco via npm instead of git submodule

…503d68fa

Use typedoc to generate API documentation

to ensure typing packages are installed.

To provide higher-level instantiation API for Ruby VM, this commit
introduces `RubyVM.instantiateComponent` and `RubyVM.instantiateModule`
methods.

Add `RubyVM.instantiateComponent` and `RubyVM.instantiateModule`

The `@ruby/wasm-wasi` package included both the Core Module and the Component
binaries but it has two problems:
1. npm package size was too large and it was very close to the limit of
   the jsdelivr CDN.
2. The Component model build (in other words, dynamic linking build)
   well supports incremental build. But the Core Module build does not
   because it requires to re-link C-extensions every time statically.
   And it led to clean build every time. Splitting out the Component
   build makes the p2 package itself incremental buildable.

…s private

I'm not confident that the name of the package, `@ruby/head-wasm-wasip2`,
is the best name for the package. So I'm marking it as private for now.

This reverts commit 54ff9a7.