Automatically adding ccs based on suspected regression changelists:

Validate that mapped buffers aren't used in submits. by cwallez@chromium.org - https://dawn.googlesource.com/dawn/+/679ff4ea86547939ac56106933dcb1a866c9a665

Add a fuzzer for the wire server and Dawn frontend by cwallez@chromium.org - https://dawn.googlesource.com/dawn/+/45ee4c88c43f2cd986a4af84ac4a8361a222b185

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

ClusterFuzz has detected this issue as fixed in range 613264:613309.

Detailed report: https://clusterfuzz.com/testcase?key=6271140642947072

Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: dawn_wire_server_and_frontend_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000018
Crash State:
  dawn_native::QueueBase::ValidateSubmit
  dawn_native::QueueBase::Submit
  dawn_wire::server::Server::HandleQueueSubmit
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=607412:607454
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=613264:613309

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6271140642947072

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing_on_windows.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6271140642947072 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

The documentation for reproducing bugs on Windows was moved to: https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md