Texture format testing

[inner-daemons]

Connections
Closes #8646

CI Failures mostly represent wgpu bugs, not issues with this PR

Description

Adds some testing for texture formats to make sure that what a device claims to support it actually supports

Testing
Is test

Squash or Rebase?
Squash

Checklist

• Run cargo fmt.
• Run taplo format.
• Run cargo clippy --tests. 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.

[ErichDonGubler]

issue: We shouldn't expose EnumIter in our public API; we've never done so before, and I think we should discuss as a group before we actually do it. In the case of EnumIter, it's usually better to make a façade around it that returns impl Iterator.

issue: Even if we do have such an opaque API, I'm not sure if it makes sense to expose an exhaustive iterator for it anyway, except for, say, an unstable-testing feature.

Thoughts?

[inner-daemons]

I'm not at all attached to my current way of doing things, this is just quick and dirty so I could set up the tests. I do very much think that we want the iteration to be automatically generated though, so that someone can't forget to add a format down the line.

[inner-daemons]

I like the idea of an extra feature here for testing, but ultimately I think the decision should be made by people more experienced with programming and with this codebase. If that makes sense to you I'm happy to do it.

[cwfitzgerald]

This is #8438

[ErichDonGubler]

question(blocking): Why do we need to derive Default here?

[inner-daemons]

This is used as a field in the Astc texture format enum variant. In order to enumerate each variant once strum needs this.

[ErichDonGubler]

I'm inclined to Move Fast and Cover Things™ for tests, but the API changes seem like something we may not want to (stably) expose for downstreams. CC @gfx-rs/wgpu for thoughts on that specifically.