v0.25.0 breaks wasm_bindgen_test usage

[istankovic]

Commit e0b735e broke our usage of rstest with wasm_bindgen_test, that typically looks like

#[apply(...)]
#[wasm_bindgen_test]
async fn foo() {
   ...
}

The errors look like:

error[E0277]: `()` is not a future
Error:    --> crypto/src/transaction_context/e2e_identity/mod.rs:161:5
    |
161 |     #[wasm_bindgen_test]
    |     ^^^^^^^^^^^^^^^^^^^^ `()` is not a future
    |
    = help: the trait `std::future::Future` is not implemented for `()`
note: required by a bound in `wasm_bindgen_test::__rt::Context::execute_async`
   --> /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wasm-bindgen-test-0.3.50/src/rt/mod.rs:509:12
    |
502 |     pub fn execute_async<F>(
    |            ------------- required by a bound in this associated function
...
509 |         F: Future + 'static,
    |            ^^^^^^ required by this bound in `Context::execute_async`
    = note: this error originates in the attribute macro `wasm_bindgen_test` (in Nightly builds, run with -Z macro-backtrace for more info)

[la10736]

#[wasm_bindgen_test] is not a valid test attribute and your case just works by chance.

Take a look at #211 (comment) on how to work around it.