Temporarily disable `Code` based profiling when VM Developer Mode is enabled (#8578)

Works around https://github.com/flutter/devtools/issues/8567 until
`package:vm_service` 15.0.0 is rolled through to Flutter.

packages/devtools_app/lib/src/service/vm_service_wrapper.dart

diff --git a/packages/devtools_app/lib/src/service/vm_service_wrapper.dart b/packages/devtools_app/lib/src/service/vm_service_wrapper.dart
index c8a906f..3e12a9b 100644
--- a/packages/devtools_app/lib/src/service/vm_service_wrapper.dart
+++ b/packages/devtools_app/lib/src/service/vm_service_wrapper.dart
@@ -20,7 +20,6 @@
 
 import '../screens/vm_developer/vm_service_private_extensions.dart';
 import '../shared/feature_flags.dart';
-import '../shared/globals.dart';
 import '../shared/primitives/utils.dart';
 import 'json_to_service_cache.dart';
 
@@ -143,7 +142,9 @@
         // running with VM developer mode enabled. This data isn't accessible
         // in non-VM developer mode, so not requesting the code profile will
         // save on space and network usage.
-        '_code': preferences.vmDeveloperModeEnabled.value,
+        // TODO(bkonyi): re-enable when package:vm_service 15.0.0 is rolled
+        // into Flutter. See https://github.com/flutter/devtools/issues/8567.
+        // '_code': preferences.vmDeveloperModeEnabled.value,
       },
     ).then((e) => e as CpuSamples);
   }