feat(crate): bump ferrflow-wasm to track main crate version

[BryanFRD]

Package
Which package does this affect? [x] cli [ ] schema [ ] docs [ ] ci

Problem / Motivation
ferrflow-wasm/Cargo.toml is at 0.1.0 while the parent ferrflow crate is at 4.7.0. Published npm @ferrflow/wasm is at 2.14.0. The playground (FerrFlow-Cloud/packages/playground/package.json) consumes 2.14.0 → the live playground runs ~v2.x logic, not the current CLI.

End result: users testing FerrFlow on ferrflow.com get behaviour ~2 majors behind the CLI they install.

Proposed solution
Acceptance criteria

Two acceptable shapes:

1. Keep WASM versioned independently with a documented version-mapping table in the README, and update it every CLI release.
2. Sync versions in the release pipeline (single source of truth). Bump the playground dep simultaneously via a Renovate / cross-repo PR.

Pick one and document it. Companion issue in FerrFlow-Cloud will bump the playground dep.

Alternatives considered
None considered explicitly — this is the natural shape.

Additional context
Severity: P1

Category: build/release

Kit / UI candidate: No.