Fix buffer usage validity in abort_over_invalid_error test

[teoxoy]

Fixes a regression introduced by #4575.

A usage of 0 is not allowed by the spec, setting it to GPUBufferUsage.STORAGE should get this test working properly.

---

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.)
• Test have be tested with compatibility mode validation enabled and behave as expected. (If not passing, explain above.)

Requirements for reviewer sign-off:

• Tests are properly located.
• Test descriptions are accurate and complete.
• Tests provide complete coverage (including validation control cases). Missing coverage MUST be covered by TODOs.
• Tests avoid over-parameterization (see case count report).

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

[github-actions]

Results for build job (at 63742bb):

 Test case/subcase counts did not change.

[kainino0x]

oops, I thought it was intentional that this made an invalid buffer (I didn't think about the fact that it would generate a validation error causing the test to fail). That just as well would have made the mapAsync calls invalid, but this makes more sense :)

LGTM