Don't require outdated wasm-bindgen feature from uuid

[Twey]

The uuid package hasn't had the feature wasm-bindgen since uuid-rs/uuid#536, in which it was renamed to js, but using it continues to work on wasm32-unknown-unknown because it accidentally activates the optional wasm-bindgen dependency that is only available on that platform.

[benthecarman]

it looks like this dep is only used in tests, could be moved to dev deps

[ptdecker]

Hello! Any update on when this fix will be merged and released? This is a blocking issue for a global upgrade we are working to move to uuid v1.9.1:

from our relevant Cargo.toml

[target.'cfg(target_arch = "wasm32")'.dependencies]
indexed_db_futures = { version = "0.4.1" }

build error:

    ... required by package `indexed_db_futures v0.4.1`
    ... which satisfies dependency `indexed_db_futures = "^0.4.1"` of package `securikey-lib v2.1.0 (/Users/ptdecker/PycharmProjects/vHSM/securikey-lib)`
versions that meet the requirements `^1.5.0` are: 1.9.1, 1.9.0, 1.8.0, 1.7.0, 1.6.1, 1.6.0, 1.5.0

the package `indexed_db_futures` depends on `uuid`, with features: `wasm-bindgen` but `uuid` does not have these features.
 It has an optional dependency with that name, but that dependency uses the "dep:" syntax in the features table, so it does not have an implicit feature with that name.


all possible versions conflict with previously selected packages.

  previously selected package `uuid v1.9.1`
    ... which satisfies dependency `uuid = "^1.9.1"` of package `securikey-lib v2.1.0 (/Users/ptdecker/PycharmProjects/vHSM/securikey-lib)`

failed to select a version for `uuid` which could resolve this conflict

[Alorel]

Fixed with 0.4.2, thanks!