feat: Inline wasm binary

[timfish]

• Ref Cannot be used with bundlers #44

No bundlers support resolving the wasm binary with the default code:

const path = require('path').join(__dirname, 'orchestrion_js_bg.wasm');
const bytes = require('fs').readFileSync(path);

That means if code gets bundled, the wasm is missing and this library cannot be used.

This PR inlines the wasm binary as a base64 string which works even if the code is bundled:

const bytes = Buffer.from('AGFzbQE...snip...', 'base64');

Downsides?

• The binary (and therefore the module) is about 33% larger
• Maybe less performant loading this way as it goes through the JavaScript parser?

[AbhiPrasad]

What if we exposed two exports? One that has the inline wasm, and one without. Then users can opt-in to inlining it.

[timfish]

What if we exposed two exports?

We can but @apm-js-collab/tracing-hooks would need to do the same.

It looks like it's quite common to inline wasm like this. It's a common webpack config:
https://github.com/search?q=%2F%5C.wasm%2F+AND+%2Fasset%5C%2Finline%2F&type=code