fix: correct option types of wasm-typescript functions

[bennypowers]

Description:

The types for the wasm-typescript functions are incorrect due to a typo.

Without this fix:

Property 'TransformConfig' is missing in type '{ module: true; filename: any; sourceMap:   • 
 true; mode: "transform"; transform: { verbatimModuleSyntax: boolean; nativeClassProperties:       
 boolean; importNotUsedAsValues: string; importExportAssignConfig: string; }; }' but required in   
 type 'Options'. [2345]  

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: a59e3543509673de64d929bcef305e5bbe044f4c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[CLAassistant]

)
All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[codspeed-hq[bot]]

CodSpeed Performance Report

Merging #9662 will degrade performances by 4.71%

_{Comparing bennypowers:patch-1 (a59e354) with main (32116a0)}

Summary

❌ 1 regressions ✅ 193 untouched benchmarks

:warning: Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	bennypowers:patch-1	Change
❌	es/full/bugs-1	524.8 µs	550.8 µs	-4.71%