Skip regress/regress-165637 on arm64.

The hard-coded timeout in the test is so near, that e.g., adding DCHECKs pushes
the test over the limit. The test is ran with dcheck_always_on=true.

We shouldn't do any performance testing with dcheck_always_on=true; this creates
the wrong incentive to not add DCHECKs (or in this case, CLs which add more
DCHECKs or cause more DCHECKs to be hit cannot land at all).

Change-Id: Ia4d1b2b17ce5a5330b929f984253c89ba273f661
Reviewed-on: https://chromium-review.googlesource.com/1046548Reviewed-by: Michael Achenbach <machenbach@chromium.org>
Commit-Queue: Marja Hölttä <marja@chromium.org>
Cr-Commit-Position: refs/heads/master@{#53032}

test/mjsunit/mjsunit.status

@@ -333,6 +333,10 @@
   'regress/regress-91013': [SKIP],
   'regress/regress-99167': [SKIP],
 
+  # Sometimes fails because the hard-coded timeout in the test is exceeded when
+  # dcheck_always_on = true.
+  'regress/regress-165637': [SKIP],
+
   # BUG(v8:3457).
   'deserialize-reference': [PASS, FAIL],