mapAsync on destroyed device

[sagudev]

Test mapAsync on destroyed device. One variant also checks that for invalid buffer on invalid device invalid device check comes first. Initially I tried to put tests in https://github.com/gpuweb/cts/blob/main/src/webgpu/api/validation/state/device_lost/destroy.spec.ts but we cannot use it's helpers because of async and we benefit from helper we have here.

Dawn passes the tests, Firefox and Servo do not.
Live preview: https://sagudev.github.io/cts/standalone/?debug=1&q=webgpu:api,validation,buffer,mapping:mapAsync,destroyedDevice:*

Spec: gpuweb/gpuweb#10971
Issue: #4708

---

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 97d7ba7):

+webgpu:api,validation,buffer,mapping:mapAsync,destroyedDevice:* - 4 cases, 4 subcases (~1/case)
-TOTAL: 287982 cases, 2362149 subcases
+TOTAL: 287986 cases, 2362153 subcases