Add tests on createBindGroupLayout() with new storage texture accesses

[Jiawei-Shao]

This patch adds tests on the use of new storage texture accesses read-only and read-write in the creation of bind group
layouts.

This patch also upgrades the version of @webgpu/types to the latest one to support these two storage texture accesses.

Note that right now this test can only pass when Chromium is launched with --enable-dawn-features=allow_unsafe_apis.

Issue: #3078

---

Requirements for PR author:

• [*] All missing test coverage is tracked with "TODO" or .unimplemented().
• [*] New helpers are /** documented */ and new helper files are found in helper_index.txt.
• [*] Test behaves as expected in a WebGPU implementation. (If not passing, explain above.)

Requirements for reviewer sign-off:

• Tests are properly located in the test tree.
• Test descriptions allow a reader to "read only the test plans and evaluate coverage completeness", and accurately reflect the test code.
• Tests provide complete coverage (including validation control cases). Missing coverage MUST be covered by TODOs.
• Helpers and types promote readability and maintainability.

When landing this PR, be sure to make any necessary issue status updates.

[Kangz]

@ben-clayton I'm surprised that Jiawei had to regenerate the cache here, is that expected?

[ben-clayton]

@ben-clayton I'm surprised that Jiawei had to regenerate the cache here, is that expected?

So the hashes will change if there's files modified that could impact the generation of the cache files. The fact the files have actually changed is likely due to differences in NodeJS versions. This is discussed here:

Since source changes will sometimes change the hash without changing the generated cache, sometimes the cache will be regenerated unnecessarily. This is OK, but try to avoid committing no-op regenerations - this will happen if your version of Node produces different gzip outputs than the original committer's Node did for the same input.

It would be good to try keeping the CTS developers on the same version of the NodeJS, and avoiding no-op regeneration like this.

[ben-clayton]

Created #3187 to try to prevent continual cache regeneration.

[jiangzhaoming]

Looks good to me, thanks

[jiangzhaoming]

So the "storage usage" mentioned here and in kTextureFormatInfo actually means supporting "write-only" or "read-only" STORAGE_BINDING in the spec, and the new added readWriteStorage means "read-write" STORAGE_BINDING.

Luckily formats that support readWriteStorage is a subset of formats that support storage (very reasonable), but I am not sure if we need to rename storage or make a comment somewhere?

[Kangz]

LGTM, I just don't understand while all these new files where created.