[baseline] Add --no-stress-concurrent-inlining for code flushing tests

--stress-concurrent-inlining disables lazy feedback allocation. These
tests require lazy feedback allocation to compile baseline code.
Listing them in INCOMPATIBLE_FLAGS_PER_VARIANT isn't sufficient for
NumFuzzer.

Bug: v8:12088
Change-Id: I4fe091d27e104f4d9acda447fcf43f9a52bf60dc
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3123420
Commit-Queue: Mythri Alle <mythria@chromium.org>
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Auto-Submit: Mythri Alle <mythria@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/main@{#76529}

test/mjsunit/baseline/flush-baseline-code.js

@@ -6,6 +6,7 @@
 // Flags: --baseline-batch-compilation-threshold=0 --sparkplug
 // Flags: --no-always-sparkplug --lazy-feedback-allocation
 // Flags: --flush-baseline-code --flush-bytecode --no-opt
+// Flags: --no-stress-concurrent-inlining
 
 function HasBaselineCode(f) {
   let opt_status = %GetOptimizationStatus(f);

test/mjsunit/baseline/flush-only-baseline-code.js

@@ -6,6 +6,7 @@
 // Flags: --baseline-batch-compilation-threshold=0 --sparkplug
 // Flags: --no-always-sparkplug --lazy-feedback-allocation
 // Flags: --flush-baseline-code --no-flush-bytecode --no-opt
+// Flags: --no-stress-concurrent-inlining
 
 function HasBaselineCode(f) {
   let opt_status = %GetOptimizationStatus(f);