Add in-docs web parser page powered by browser WASM

[1technophile]

Description:

Adds a /parser page on the VitePress site that decodes BLE advertisements locally in the browser via a new BUILD_WASM_WEB Emscripten target (ENVIRONMENT=web,worker, EXPORT_ES6, SINGLE_FILE), built fresh by the docs publish workflow on each release. The Node.js WASM build shipped to npm is untouched.

Checklist:

• The pull request is done against the latest development branch
• Only one feature/fix was added per PR and the code change compiles without warnings
• I accept the DCO.

[1technophile]

@mhaberler feel free to share your comments

[mhaberler]

how can I preview this?
lost in build land :-/

ping @1technophile

[1technophile]

Try this @mhaberler :

1. Get Emscripten on your PATH (CI uses 3.1.61, any recent emsdk works):
   git clone https://github.com/emscripten-core/emsdk.git
   cd emsdk && ./emsdk install 3.1.61 && ./emsdk activate 3.1.61
   source ./emsdk_env.sh # puts emcmake/emmake on PATH

2. Build the browser WASM (from the repo root):
   cd nodejs/theengs-decoder
   npm install
   npm run build:web
   That runs emcmake cmake -DBUILD_WASM_WEB=ON + emmake make, then copies the single-file ES6 module into
   docs/.vitepress/public/wasm/theengs_decoder_web.js.

3. Run the docs site (from the repo root):
   npm install
   npm run docs:dev
   Then open the /parser page — it should load the decoder and decode the sample payload.

[mhaberler]

LGTM - got it to work as outlined

if you merge this just close my PR

do you see any downside in one module for both use cases?

[1technophile]

Going to update this PR to have one unified esm module