[sparkplug][test] Fix NumFuzz (mjsunit/baseline/batch-compilation.js)

--stress-concurrent-inlining has a negative implication for
--lazy-feedback-allocation. We need to explicitly add
--no-stress-concurrent-inlining, since the test relies on lazy feedback
allocation.

Bug: v8:11853
Change-Id: I2bd8f0da05a766dd7282cdb3b70c4a1b478c71cc
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2948647
Commit-Queue: Patrick Thier <pthier@chromium.org>
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#75037}

test/mjsunit/baseline/batch-compilation.js

@@ -3,9 +3,14 @@
 // found in the LICENSE file.
 
 // Flags: --sparkplug --no-always-sparkplug --sparkplug-filter="-"
-// Flags: --allow-natives-syntax --expose-gc --lazy-feedback-allocation
+// Flags: --allow-natives-syntax --expose-gc
 // Flags: --baseline-batch-compilation --baseline-batch-compilation-threshold=200
 
+// Flags to drive Fuzzers into the right direction
+// TODO(v8:11853): Remove these flags once fuzzers handle flag implications
+// better.
+// Flags: --lazy-feedback-allocation --no-stress-concurrent-inlining
+
 // Basic test
 (function() {
   // Bytecode length 24 -> estimated instruction size 120 - 168.