Adding ccs from non-trivial CLs in the regression range.

Clusterfuzz is awesome.

The sanity check in VerifyApiCallResultType doesn't know about BigInts yet. No security implications.

Fix: https://chromium-review.googlesource.com/#/c/v8/v8/+/957422

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/0c0847bea49c61214eb734c2caa8068d13504ec0

commit 0c0847bea49c61214eb734c2caa8068d13504ec0
Author: Jakob Kummerow <jkummerow@chromium.org>
Date: Sat Mar 10 02:47:20 2018

[bigint] Fix Object::VerifyApiCallResultType

Add BigInt to the list of allowed result types.

Bug:  v8:6791 ,  chromium:819871 
Change-Id: Ib636859da07b38c462ce7017d720e5370ba618d6
Reviewed-on: https://chromium-review.googlesource.com/957422
Reviewed-by: Adam Klein <adamk@chromium.org>
Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#51859}
[modify] https://crrev.com/0c0847bea49c61214eb734c2caa8068d13504ec0/src/objects-inl.h
[modify] https://crrev.com/0c0847bea49c61214eb734c2caa8068d13504ec0/test/mjsunit/harmony/bigint/regressions.js

ClusterFuzz has detected this issue as fixed in range 51858:51859.

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8_dbg
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  API call returned invalid object in objects-inl.h
  v8::platform::PrintStackTrace
  v8::internal::Object::VerifyApiCallResultType
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=51672:51675
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=51858:51859

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

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.

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

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