[test] Don't test the profiler in a test with a large number of threads.

TSAN's vector clocks become more expensive as the number of threads that touch a variable increases. The Mac/Windows/Fuchsia profilers will sample threads by suspending it and accessing it from another thread.

TEST=ci
Bug: #61960
Change-Id: I2bfb7908af8ff864bc52577bacbb89a4778150d0
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/465980
Reviewed-by: Alexander Aprelev <[email protected]>
Commit-Queue: Ryan Macnak <[email protected]>

Author: rmacnak-google

tests/ffi/many_listener_callbacks_test.dart

@@ -11,10 +11,13 @@
 // VMOptions=--use-slow-path --stacktrace-every=100
 // VMOptions=--dwarf_stack_traces --no-retain_function_objects --no-retain_code_objects
 // VMOptions=--test_il_serialization
-// VMOptions=--profiler --profile_vm=true
-// VMOptions=--profiler --profile_vm=false
 // SharedObjects=ffi_test_functions
 
+// No profiler for this test. TSAN's vector clocks become more expensive as the
+// number of threads that touch a variable increases. This test creates many
+// threads, and the Mac/Windows/Fuchsia profilers will sample them from another
+// thread.
+
 import 'dart:async';
 import 'dart:ffi';