Support other socket standards

[gkgoat1]

While WASI 0.2 and the Component Model are incredibly powerful, the format is tricky for consumers to use. A core-module-emitting target would help adoption of StarlingMonkey, and further its independent use.

There are two standards ol note: WasmEdge's socket extension to WASI 0.1, and WASIX, a POSIX-flavored (not fully capability-based) revival of WASI 0.1; both emit core modules, allowing existing tooling, especially compilers to work with them. Supporting one or both standards would allow rehosting JS programs within other, core-wasm-expecting, frameworks. WASIX, in particular, uses its own embedding of SpiderMonkey; merging it in and using StarlingMonkey for everything would standardize the interface: both the internal API and the external ABI.

Note that wasit2, a core module target for WASI 0.2 won't help here; Canonical ABI information is lost, so embedders either have to finalize the component creation process or guess the Canonical ABI information used.