lazy-feedback-allocation conflicts with stress-concurrent-inlining

stress-concurrent-inlining has a negative implication for
lazy-feedback-allocation. So add lazy-feedback-allocation as
incompatible flag with stress-concurrent-inlining.

Bug: v8:12088, v8:11947
Change-Id: Ia8ff66c595f6c6288b44f7a066729ace0d7ad9d8
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3113630
Commit-Queue: Mythri Alle <mythria@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/main@{#76483}

test/mjsunit/mjsunit.status

@@ -1063,8 +1063,6 @@
   'baseline/test-osr': [SKIP],
 
   # BUG(v8:11826) Skipped until we remove flakes on NumFuzz.
-  'baseline/flush-only-baseline-code': [SKIP],
-  'baseline/flush-baseline-code': [SKIP],
   'regress/wasm/regress-1231950': [SKIP],
 
   # BUG(v8:12013) Skipped until we remove flakes on NumFuzz.

tools/testrunner/local/variants.py

@@ -57,7 +57,8 @@ INCOMPATIBLE_FLAGS_PER_VARIANT = {
   "nooptimization": ["--always-opt"],
   "slow_path": ["--no-force-slow-path"],
   "stress_concurrent_allocation": ["--single-threaded-gc", "--predictable"],
-  "stress_concurrent_inlining": ["--single-threaded", "--predictable", "--turboprop"],
+  "stress_concurrent_inlining": ["--single-threaded", "--predictable",
+                                 "--turboprop", "--lazy-feedback-allocation"],
   "turboprop": ["--stress_concurrent_inlining"],
   # The fast API tests initialize an embedder object that never needs to be
   # serialized to the snapshot, so we don't have a