Add expected_msg_substring arg. to wgpu_test::fail

[ErichDonGubler]

Connections
Link to the issues addressed by this PR, or dependent PRs in other repositories

Motivated by discussion in (and based on code from) another PR: #5282 (comment)

• After merge: file good first issue for converting more tests to use specific validation error messages: Good first issue: use concrete error messages for wgpu-test tests #5727

Description
Describe what problem this is solving, and how it's solved.

Until now, we accept any validation failure inside a callback passed to wgpu_test::fail. This is a very broad error condition, and may allow errors for the wrong reason. Now, we'd like to tighten up the failures that we actually expect from these tests. Also, this would let us factor out some error scope boilerplate introduced for the tests in #5282.

Testing
Explain how this change is tested.

This is a refactor of tests to make them more narrow, and they still pass. ✅

Checklist

• Run cargo fmt.
• Run cargo clippy. If applicable, add:
  • --target wasm32-unknown-unknown
  • --target wasm32-unknown-emscripten
• Run cargo xtask test to run tests.
• Add change to CHANGELOG.md. See simple instructions inside file. Seems like none should be necessary here?

[Wumpf]

nice! I did something similar here, but in a less intrusive way (because the pr shouldn't also drag in such a large refactor)

https://github.com/gfx-rs/wgpu/pull/5671/files#diff-aeefe6b3d3f8b1b5248d6bb4c2888cf2d6802dbf82515f7b02b6a89a1400228fR35

(will happily move my stuff to this new variant once we get the stuff that comes before it merged :/)

[ErichDonGubler]

Rebasing required migrating new tests from #5715, resulting in 7d40e5b and 7bccffb.