Added support for the wasm32v1-none target

[daxpedda]

This PR adds support for the wasm32v1-none target and should enable all features previously behind cfg(feature = "std") for both wasm32-unknown-unknown and wasm32v1-none. Additionally, now js-sys, web-sys, wasm-bindgen-futures and wasm-bindgen-test support no_std.

Changes:

• Use any(target_os = "unknown", target_os = "none") instead of target_os = "unknown".
• For globals:
  • Continue to use once_cell::sync::Lazy when targeting std.
  • Use Send + Sync wrapped once_cell::unsync::Lazy when targeting no_std without target_feature = "atomics".
  • Use once_cell/critical_section when targeting no_std with target_feature = "atomics". As recommended by critical_section, this is something the user has to enable. Notable this only affects link_to!, any other feature will work as expected with no additional work required from the user.
• For thread locals:
  • Continue to use std::thread_local! when targeting std.
  • Use static mut when targeting no_std without target_feature = "atomics".
  • Use #[thread_local] when targeting no_std with target_feature = "atomics".
• Add std crate feature to js-sys, web-sys, wasm-bindgen-futures and wasm-bindgen-test and enable by default. This makes it possible to use these crates with no_std for both targets as well.
• Inlined console_error_panic_hook and a no_std version of scoped_tls.

Missing:

• Add wasm32v1-none to CI. Probably in a follow-up when its stable, ergo Rust v1.84.

[RunDevelopment]

I think thread_local_v2 still needs to be documented, right?

[daxpedda]

I think thread_local_v2 still needs to be documented, right?

I had just amended the already existing documentation which wasn't very clear. I improved it a bit now.