feat(op_crates): webgpu

[crowlKats]

Closes #7863

missing:

• create navigator & workerNavigator and add webgpu to them
• create a webgpu instance with the op_webgpu_create_instance op now handled at init and set in OpState
• get op_webgpu_buffer_get_map_async to work
• have the slice in op_webgpu_buffer_get_mapped_range be put into zero_copy
• fix PassChannel structs
• TS types
• Move TS types to unstable (do this in follow up)
• WPT tests (do this in follow up)
• Resource cleanup
• WebIDL
• Implement Deno.customInspect
• add [[device]] internal slot to all objects except adapter
• closes resources on finalization for consumables
• Cleanup automatically using FinalizationRegistry (do this in follow up)
• validate that objects belong to same device
• check if objects are valid before using them (check if rid is present)

Examples can be found at https://github.com/crowlKats/webgpu-examples/

[ry]

I did some size comparisons with main branch:

webgpu
target/debug/deno 248M
target/release/deno 72M

main
target/debug/deno 212M
target/release/deno 66M

Quite a bit larger.

[ry]

This is an epic feature that opens the door to doing serious scientific computing with JavaScript. We will likely be able to run TensorFlow.js on Deno without too much work after this. Having a dynamic runtime with easy GPU access is a game changer.

@crowlKats and @lucacasonato have been working on this for months - it's hard to understate the effort that they have put in to deliver this branch. Thank you for your work on this!

• Superficially the code looks good to me.
• My main concern is the complete lack of tests. I understand that in the future we are aiming for WPT coverage for WebGpu, but that it will require more work to get there. That's ok, but for the time being we ought to add some basic smoke tests that exercise various parts of the API.
• I also think a large crate like this should have a README with an introduction to the code base - some description of how it's organized, links to docs, and a todo list future work.
• It should be noted (probably in README) that CI cannot test because Github Actions runners do not have GPUs (except for windows). This is scary.
• I am also concerned about the 8mb size increase (this on top of the ICU size increase would make Deno 1.8 50% larger than 1.7) but it doesn't seem like there's much we can do about that.

[ry]

LGTM :)

[lucacasonato]

Huge thanks @crowlKats and @kvark!