Fix separate depth stencil read-only state

[beicause]

Connections
Fixes #5231.
Fixes #8705.

Description
Fix separate depth stencil read-only state on vulkan and dx12 (metal seems already works).

Splits DEPTH_STENCIL_READ/DEPTH_STENCIL_WRITE TextureUses into separate depth and stencil states. On vulkan, it needs VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL and VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL which requires vulkan 1.1 or VK_KHR_maintenance2.

Additionally, we internally use VK_ATTACHMENT_STORE_OP_NONE (or its variants provided by extensions) to avoid the SYNC_HAZARD_WRITE_AFTER_WRITE validation error. If VK_ATTACHMENT_STORE_OP_NONE is not supported, we have to insert barrier with write access flag for readonly depth stencil to avoid that error.

Testing

cargo xtask cts 'webgpu:api,operation,memory_sync,texture,readonly_depth_stencil:*'
cargo r -p wgpu-examples water

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.

TODO:

• Fix dx12