CTS failures in `depth_stencil_attachment_and_bind_group`

[andyleiserson]

All of the tests in the webgpu:api,validation,resource_usages,texture,in_render_common:subresources,depth_stencil_attachment_and_bind_group:* group are failing with:

  - EXCEPTION: Error: Unexpected validation error occurred: In a pass parameter: Attempted to use Texture with '' label (mips 1..2 layers 1..2) with conflicting usages. Current usage TextureUses(RESOURCE) and new usage TextureUses(DEPTH_STENCIL_WRITE). TextureUses(DEPTH_STENCIL_WRITE) is an exclusive usage and cannot be used with any other usages within the usage scope (renderpass or compute dispatch).
        at DeviceHolder.attemptEndTestScope (file:///Users/Andy/Development/wgpu/cts/out/webgpu/util/device_pool.js:466:13)
        at eventLoopTick (ext:core/01_core.js:179:7)
        at async DevicePool.release (file:///Users/Andy/Development/wgpu/cts/out/webgpu/util/device_pool.js:104:7)
        at async Promise.allSettled (<anonymous>)
        at async AllFeaturesMaxLimitsGPUTestSubcaseBatchState.finalize (file:///Users/Andy/Development/wgpu/cts/out/webgpu/gpu_test.js:154:21)
        at async RunCaseSpecific.run (file:///Users/Andy/Development/wgpu/cts/out/common/internal/test_group.js:696:9)
        at async file:///Users/Andy/Development/wgpu/cts/out/common/runtime/cmdline.js:218:5

Referring to the conditions in the test, I believe it is the inSamePass && !isNotOverlapped && readonly case that is problematic (the tests pass if I add an early return under this condition). i.e., the case where even though binding and attachment are on the same render pass and are overlapping, the usage is still allowed because it is read-only. That we are talking about DEPTH_STENCIL_WRITE in the error seems suspicious.