[compiler] Fix and re-enable tests requiring specific optimization timing

We now have %FinalizeOptimization() to block until all concurrent
compile jobs are done.

Bug: v8:7790,v8:12004
Change-Id: Ibb9955be06957b3f395b680e9be570c7c3ec0dcb
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3086478
Auto-Submit: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Georg Neis <neis@chromium.org>
Reviewed-by: Georg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#76231}

test/mjsunit/interrupt-budget-override.js

@@ -16,4 +16,5 @@ function f() {
 f();
 f();
 f();
+%FinalizeOptimization();
 assertOptimized(f);

test/mjsunit/mjsunit.status

@@ -207,12 +207,6 @@
   'regress/regress-crbug-941743': [PASS, HEAVY],
   'regress/regress-crbug-1191886': [PASS, HEAVY],
   'wasm/externref-globals': [PASS, HEAVY],
-
-  # Unpredictable results due to assertOptimized with concurrent optimization.
-  # TODO(v8:12004): Add a runtime function to flush the optimizing compile
-  # dispatcher *without* aborting existing jobs.
-  'interrupt-budget-override': [PASS,FAIL],
-  'never-optimize': [PASS,FAIL],
 }],  # ALWAYS
 
 ##############################################################################

test/mjsunit/never-optimize.js

@@ -43,5 +43,6 @@ for (let i = 0; i < 1000; ++i) {
   u1();
   u2();
 }
+%FinalizeOptimization();
 assertUnoptimized(u1);
 assertOptimized(u2);