[metal] Metal compute shader passthrough

[syl20bnr]

Description
This PR adds the possibility to directly pass a metal shader and create a compute pipeline to execute the passed shader without any validation. This allows CubeCL to use its wgpu runtime to execute metal kernels directly compiled by CubeCL JIT compiler and benefit from support for advanced metal features.

Testing
Tested with a WIP metal compiler using the wgpu runtime of CubeCL.
More info about how to test this soon.

Squash or Rebase?

Ok to be squashed.

Checklist

• Run cargo fmt.
• Run taplo format.
• Run cargo clippy. If applicable, add:
  • --target wasm32-unknown-unknown
• Run cargo xtask test to run tests.
• If this contains user-facing changes, add a CHANGELOG.md entry.

[cwfitzgerald]

I think we should unify this entrypoint with create_shader_module_spirv and call it create_shader_module_passthrough which takes a ShaderModulePassthrough enum with each descriptor as needed.

This is cool!

[cwfitzgerald]

It would be great to get some description of the shader ABI we present to shaders and how things get translated. It doesn't need to be as strict as in wgpu-hal, but should guide people on what wgpu expects the shader to have.

[DJMcNab]

(Linking to #3103)

[syl20bnr]

@cwfitzgerald Thank you for the review.

I think we should unify this entrypoint with create_shader_module_spirv and call it create_shader_module_passthrough which takes a ShaderModulePassthrough enum with each descriptor as needed.

I pushed a simple change for this, is that what you had in mind ?

It would be great to get some description of the shader ABI we present to shaders and how things get translated. It doesn't need to be as strict as in wgpu-hal, but should guide people on what wgpu expects the shader to have.

Not sure what do you mean, do you have an example of such description ?

Also can you point me to where I could add a test for the metal passthrough if needed ?