Don't include detailed shader compilation info in validation error

[beicause]

Connections

Description

Don't include detailed shader compilation info in validation error

See https://gpuweb.github.io/gpuweb/#dom-gpudevice-createshadermodule :

NOTE:
User agents should not include detailed compiler error messages or shader text in the message text of validation errors arising here: these details are accessible via getCompilationInfo(). User agents should surface human-readable, formatted error details to developers for easier debugging (for example as a warning in the browser developer console, expandable to show full shader source).

As shader compilation errors should be rare in production applications, user agents could choose to surface them to developers regardless of error handling (GPU error scopes or uncapturederror event handlers), e.g. as an expandable warning. If not, they should provide and document another way for developers to access human-readable error details, for example by adding a checkbox to show errors unconditionally, or by showing human-readable details when logging a GPUCompilationInfo object to the console.

Testing
Added an unit test in wgpu-core/src/pipeline.rs

Squash or Rebase?
Squash

Checklist

• I self-reviewed and fully understand this PR.
• WebGPU implementations built with wgpu may be affected behaviorally.
• Validation and feature gates are in place to confine behavioral changes.
• Tests demonstrate the validation and altered logic works.
• CHANGELOG.md entries for the user-facing effects of this change are present.
• The PR is minimal, and doesn't make sense to land as multiple PRs.
• Commits are logically scoped and individually reviewable.
• The PR description has enough context to understand the motivation and solution implemented.

[kpreid]

In wgpu, there is no such thing as “the developer console”. While this specified behavior should be available in wgpu-core for the sake of implementing WebGPU to spec, I don’t think it should be the behavior that wgpu exposes to Rust users.

Perhaps a good compromise would be that the compilation error appears as the source() of the validation error. This means that normal Rust error printers can include the details automatically, but that a short message is also available.

[beicause]

I left ShaderError in source(), though this requires special handling to skip it when recursively format error descriptions in wgpu and deno_webgpu.