🐛 Configure esbuild-wasm initialize to use installed package version

[balajis-qb]

Description

Configures esbuild-wasm’s initialize to load the WASM from a URL pinned to the installed package version, preventing mismatches between the JS wrapper and the WASM binary. Also upgrades esbuild-wasm to 0.25.10.

Problem
Using an unpinned WASM URL could fetch a different version than the installed esbuild-wasm JS, causing runtime errors and version conflicts.

Linked PR: #5865

Changes

• Configure initialize to use: https://unpkg.com/esbuild-wasm@${version}/esbuild.wasm
• Upgrade esbuild-wasm to 0.25.10.

Contribution checklist

• I have followed the contributing guidelines.
• I have formatted my code with Prettier and checked for linting issues with ESLint for code readability.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.26%. Comparing base (8b4935e) to head (ac7bd94).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5893   +/-   ##
=======================================
  Coverage   97.26%   97.26%           
=======================================
  Files          30       30           
  Lines        3443     3443           
  Branches     1439     1439           
=======================================
  Hits         3349     3349           
  Misses         94       94           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[balajis-qb]

@martijnrusschen, Could you please review and merge this fix PR. Currently the transpilation is failing because the esbuild-wasm version conflict.