Stop invalidating warm builds by rewriting generated module maps

Side-effect execution now leaves active generated dependency module maps and framework search path response files untouched when their bytes already match, so warm tuist test --build-only invocations no longer invalidate Swift compilation between reruns. Stale -deps.modulemap and .resp files in Derived/ModuleMaps and Derived/FrameworkSearchPaths are still removed, using scoped include patterns so external SwiftPM module maps like Package.modulemap are never deleted.