Remove slow and pointless test code

It looks like the loop is there to create objects and trigger GC. It's
also tailored to Crankshaft, which was removed long ago.
This code currently times out on some arm bots, and it's hard to see
any value in it. Thus remove it.

R=mslekova@chromium.org

Change-Id: Ia47d4f70d679f79cfea523f467ff7adc3360cf6c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1793065Reviewed-by: Maya Lekova <mslekova@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#63630}

test/mjsunit/bit-not.js

@@ -62,16 +62,3 @@ testBitNot(0x80000000 - 0.12345, "float6");
 testBitNot("0", "string0");
 testBitNot("2.3", "string2.3");
 testBitNot("-9.4", "string-9.4");
-
-
-// Try to test that we can deal with allocation failures in
-// the fast path and just use the slow path instead.
-function TryToGC() {
-  var x = 0x40000000;
-  // Put in an eval to foil Crankshaft.
-  eval("");
-  for (var i = 0; i < 1000000; i++) {
-    assertEquals(~0x40000000, ~x);
-  }
-}
-TryToGC();