Support custom WASM locations in the QuickJS isolate driver

[SilvioYMollov]

Problem

Applications may need to serve the QuickJS WASM binary from a public directory or CDN instead of relying on the location resolved by
quickjs-emscripten.

This is particularly useful in browser, edge, and bundled environments where the default WASM asset location is unavailable or unsuitable.

Proposed API

Add an OPTIONAL wasmLocation setting:

const driver = createQuickJSIsolateDriver({
  wasmLocation: '/assets/quickjs/emscripten-module.wasm',
})

When omitted, the existing quickjs-emscripten loading behavior remains
unchanged.