Avoid using WasmAbi functions on WebGPU backend

[grovesNL]

Checklist

• Run cargo clippy.
• Run RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown if applicable.
• Add change to CHANGELOG.md. See simple instructions inside file.

Connections
Fixes #3430

Description
IntoWasmAbi and FromWasmAbi can be problematic for our use case because IntoWasmAbi takes ownership of our type. We could workaround this in different ways, but the most straightforward path right now seems to be to avoid using these entirely and instead not tracking IDs for the WebGPU backend.

We could look at doing this in a few different ways once we internally make some changes to better support multi-threading (e.g., many types will be Arc internally so we could consider some other approaches).

Testing
Tested the WebGPU examples that are known to work (hello-triangle, boids, msaa-line, etc.) in Canary.

[niklaskorz]

Tried it on https://github.com/niklaskorz/linon/tree/dynamic-dispatch-workaround and it works (deployed on https://niklaskorz.github.io/linon/):

A note though (that might be unrelated to this PR, not sure): using depth textures without a stencil part in the format does not seem to work in Chrome, i.e. using Depth32Float instead of Depth24PlusStencil8 gives this error, even though no stencil ops are actually set in the render pass:

stencilLoadOp is (LoadOp::Load) and stencilStoreOp is (StoreOp::Store) when stencilReadOnly (0) or the attachment ([TextureView of Texture "depth_texture"]) has no stencil aspect.
 - While validating depthStencilAttachment.
 - While encoding [CommandEncoder "encoder"].BeginRenderPass([RenderPassDescriptor "rpass"]).

[Invalid CommandBuffer "encoder"] is invalid.
    at ValidateObject (..<URL>)
    at ValidateSubmit (..<URL>)

localhost/:1 WebGPU: too many warnings, no more warnings will be reported to the console for this GPUDevice.

Edit: ok this is indeed unrelated to this PR but it's an existing bug in wgpu, I'll try to fix it :)

[cwfitzgerald]

All seems reasonable, thank you for taking the time to fix this!