Found while investigating #25021

ElectronBrowserMainParts has a periodic timer that is used to trigger GC once a minute even on an idle system. While one wakeup per minute isn't bad, it's also been in there [since 2014](https://github.com/electron/electron/commit/4dd78480846557370dd53789d50e6cb0d6a81bcd) and may or may not still be necessary. It might be worth seeing what happens to memory overhead if this is disabled and/or triggered with a different mechanism.

```c++
  // Start idle gc.
  gc_timer_.Start(
      FROM_HERE, base::TimeDelta::FromMinutes(1),
      base::Bind(&v8::Isolate::LowMemoryNotification,
                 base::Unretained(js_env_->isolate())));
```


shell/browser/electron_browser_main_parts.cc
DCHECK(base::ThreadTaskRunnerHandle::IsSet());
  
  
  js_env_ = std::make_unique<JavascriptEnvironment>(node_bindings_->uv_loop());
  v8::HandleScope scope(js_env_->isolate());
  node_bindings_->Initialize();
  
  node::Environment* env = node_bindings_->CreateEnvironment(
      js_env_->context(), js_env_->platform());
  node_env_ = std::make_unique<NodeEnvironment>(env);
  env->set_trace_sync_io(env->options()->trace_sync_io);
  
  electron_bindings_->BindTo(js_env_->isolate(), env->process_object());
  
  node_bindings_->LoadEnvironment(env);
  
  node_bindings_->set_uv_env(env);
  
  
  
  
  base::FeatureList::ClearInstanceForTesting();
  InitializeFeatureList();
  
  fake_browser_process_->PostEarlyInitialization();
}
int ElectronBrowserMainParts::PreCreateThreads() {