Generated dependency module maps keep stable mtimes across warm builds

Warm tuist test –build-only invocations stay incremental again for projects whose targets reference generated dependency module maps. The graph mappers no longer rewrite a generated file when its bytes are already correct (so generated Derived/ModuleMaps/-deps.modulemap and Derived/FrameworkSearchPaths/.resp mtimes stay stable), Derived/ModuleMaps and Derived/FrameworkSearchPaths are preserved during the early Derived cleanup, and stale Tuist-owned files are removed by a declarative GeneratedFilesCleanupDescriptor executed in SideEffectDescriptorExecutor with scoped include patterns so external module maps like Package.modulemap are not deleted.