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:

[Extensions Bindings] Add a fieldtrial testing config entry for native bindings by rdevlin.cronin@chromium.org - https://chromium.googlesource.com/chromium/src/+/0ef734f4659e2af652b6846e073be226cd11de6d

[Squad] Rename cached/uncached pseudo style methods. by futhark@chromium.org - https://chromium.googlesource.com/chromium/src/+/5bc9720b1e3d2c438ac6ab7b70d9d27c608ffaa8

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

Definitely looks like the extensions one.

ClusterFuzz has detected this issue as fixed in range 571353:571356.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000020
Crash State:
  get
  extension
  extensions::AppBindingsCore::GetIsInstalled
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=569274:569278
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=571353:571356

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

See https://github.com/google/clusterfuzz-tools for more information.

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