fix: service-worker

[lalyos]

I was unable to reproduce the yt wanix demo, where a new Iframe's src points to opfs via /:/web/opfs.
I found 2 issues, the service worker wasn't registered, and once it was it was caching the opfs file, so any change had no effect.

[lalyos]

this was my test:

cat > /web/opfs/iframe.sh <<'EOF'
[ -e /web/opfs/a.txt ] || echo hello > /web/opfs/a.txt
cd /web/dom
id=$(cat new/iframe)
echo append-child $id >> body/ctl
echo src=/:/web/opfs/a.txt >> $id/attrs
EOF
chmod +x /web/opfs/iframe.sh
./iframe.sh

[progrium]

cool. i know stuff has probably broken since last release (but also more developed). i'm curious what are the changes to the wasi worker lib.js?

[lalyos]

Hmmm actually I'm not sure where those changes originated?!
I just saw that runtime/wasi/worker/lib.js is generated by esbuild,
and thought maybe I got a newer esbuild version, as te changes seemed minor/cosmetic.

But deleted it and tried to regenerate ... and couldn't.

So just removed that commit from the PR, and it still fixes the 404 error reproducible by iframe.sh

[lalyos]

I was thinking that as we already use cloudflare:
We could use its pages feature for being able to deploy every commit/branch on its on preview url. So a PR could be easily checked by letting cf-pages serve a static dir from wanix export + the bundle.tgz