Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on suspected regression changelists:

Remove using std::<foo> statements. (#1756) by dj2@everburning.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/a5a5ea0e2dfce9c755a88af1074ebe68a44d2ed9

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

With reference to the  Issue 874022 , merging this issue into 873225

ClusterFuzz has detected this issue as fixed in range 586353:586375.

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

Fuzzer: libFuzzer_spvtools_opt_legalization_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000028
Crash State:
  spvtools::opt::Instruction::opcode
  spvtools::opt::Instruction::GetBaseAddress
  spvtools::opt::MemPass::GetPtr
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=580292:580305
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=586353:586375

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

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

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