Record 1 barrier for N Queue::write_buffer/texture calls by deferring to submit time

[JMS55]

Connections
Fixes #6673

Description
Instead of recording a barrier for the staging buffer immediately when Queue::write_buffer/texture is called, defer it to submit time, so that only a single barrier is needed for N writes.

This only works for the first time you write to a resource (I think per submit?), with subsequent writes reverting back to immediate barriers (23a82b5).

Subresource ranges are also not tracked, barriers are still per-resource.

Testing
TODO

Squash or Rebase?
Squash

Checklist

• I self-reviewed and fully understand this PR.
• 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.
• (If applicable) WebGPU implementations built with wgpu may be affected behaviorally.
• (If applicable) Validation and feature gates are in place to confine behavioral changes.
• (If applicable) Tests demonstrate the validation and altered logic works.

[cwfitzgerald]

Oh nice, I've had implementing something like this in the back of my mind for ages now

[cwfitzgerald]

Sorry I'm just testing something I haven't actually looked at this yet

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

Testing

[cwfitzgerald]

Testing again

Testing