Bump wasm-bindgen-utils to 0.1.2 in rainlang-eval (remove the duplicate 0.0.x utils in downstream locks)

[thedavidmeister]

Problem

After raindex moved its Rust deps to crates.io and bumped rain-math-float to 0.1.5 (utils 0.1.2), the workspace lock still resolves two copies of wasm-bindgen-utils:

• 0.1.2 — everything (rain-math-float, rain-metadata, the published rainlang bindings/dispair/parser, raindex itself)
• 0.0.10 — pulled in only by the rainlang-eval git dep (rainlanguage/rainlang @ 77ffb9f2), which still depends on the old wasm-bindgen-utils 0.0.x.

cargo tree -i wasm-bindgen-utils@0.0.10 →

wasm-bindgen-utils v0.0.10
└── rainlang-eval ...
    └── raindex_common → raindex_cli / raindex_js_api / raindex_rest_api ...

This is currently harmless (eval is native-only — foundry-evm — so its #[wasm_bindgen] surface is inert), but it leaves a stale, semver-incompatible second copy of the prelude in every downstream lock and blocks a clean single-version cutover.

Task

• Bump wasm-bindgen-utils from 0.0.x to 0.1.2 in rainlang-eval (and any other rainlang workspace crate still on 0.0.x), aligning with rain-math-float/rain-metadata.
• If rainlang-eval declares #[wasm_bindgen] opaque-class structs, add wasm-bindgen as a direct dependency to avoid the unbounded macro-recursion bug (see rain.math.float#226).
• Cut a rainlang rev with the bump so raindex re-pins eval/test_fixtures to it and the lock collapses to a single wasm-bindgen-utils 0.1.2.

Related: rainlang#519 (publishing eval + test_fixtures to fully drop the git deps).