feat(ci): parse wasm-bindgen version to install correct client

[ThierryBerger]

Fix #83

Prevent wasm CI from crashing when a Cargo.lock is committed and a new version of wasm-bindgen-cli is released, effectively installed via its name only in CI, but incompatible with the old one from the lockfile.

This PR addresses this by parsing cargo metadata and installing the same version.

[ChristopherBiscardi]

I don't really see how this fixes the "issue" since the wasm-bindgen version used in the Cargo.lock is the version that needs to match, and this PR will thus just invert the problem, leading to an old version in CI and a new version in lock.

The relevant CI for your failed CI run shows that you installed wasm-bindgen .106: https://github.com/ThierryBerger/tb_ly/blob/e1167e513e300792aff1bec947d1e139e2358f55/Cargo.lock#L7873

So this is because you have a different version installed in your project vs ci, which isn't really a thing the template can fix by pinning to an old version

[ThierryBerger]

Thanks for the precisions! I agree that my fix is indeed incorrect (as it will now fail most of the cases).

End users tend to commit their cargo.lock though, and when they do, the next update of wasm-bindgen-cli will break the CI, so I think the root issue is worth debating at least.

[mockersf]

you can find the version to install with cargo metadata --format-version 1 | jq --raw-output '.packages[] | select(.name=="wasm-bindgen") | .version'

[ChristopherBiscardi]

lockfile version detection is much better than pinning

[alice-i-cecile]

@ThierryBerger can you please update the PR description/title? Once that's done I'm happy to merge.

[ThierryBerger]

@alice-i-cecile I updated the title and description.