[bun:test] Don't schedule the GC aggressively on every file

We already run the GC automatically whenever heap size grows, so this is mostly unnecessary

In one benchmark, this is an 83% performance improvement at a cost of 9% more memory

1 files changed, 10 insertions, 1 deletions

diff --git a/src/cli/test_command.zig b/src/cli/test_command.zig
index 8330a786b..3fdce584a 100644
--- a/src/cli/test_command.zig
+++ b/src/cli/test_command.zig
@@ -746,6 +746,7 @@ pub const TestCommand = struct {
             }
 
             const file_end = reporter.jest.files.len;
+
             for (file_start..file_end) |module_id| {
                 const module = reporter.jest.files.items(.module_scope)[module_id];
 
@@ -770,7 +771,15 @@ pub const TestCommand = struct {
                         prev_unhandled_count = vm.unhandled_error_counter;
                     }
                 }
-                _ = vm.global.vm().runGC(false);
+                switch (vm.aggressive_garbage_collection) {
+                    .none => {},
+                    .mild => {
+                        _ = vm.global.vm().collectAsync();
+                    },
+                    .aggressive => {
+                        _ = vm.global.vm().runGC(false);
+                    },
+                }
             }
 
             vm.global.vm().clearMicrotaskCallback();