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

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

Predator has provided 26 possible suspects.
Unable to find the suspect CL hence adding CF-NeedsTriage label

Since stevenperron@ has maximum changes in suspect list, cc'ing  him for further triage.

Fixed with https://github.com/KhronosGroup/SPIRV-Tools/pull/1835, but it is also an invalid test case that the validator accepts.  We can improve the validator as well.

ClusterFuzz has detected this issue as fixed in range 583087:583101.

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

Fuzzer: libFuzzer_spvtools_opt_performance_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  rebuilt->IsSame(&type)
  spvtools::opt::analysis::TypeManager::RegisterType
  spvtools::opt::analysis::TypeManager::GetTypeInstruction
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=579911:580305
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=583087:583101

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

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.

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

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