Keep incremental builds warm with stable generated module map timestamps

Warm tuist test –build-only invocations stay incremental again when generated dependency module maps are involved. Tuist now preserves the modification times of unchanged generated files, keeps generated module maps and framework search path directories across cleanup, and removes only stale generated files that match Tuist-owned patterns. This avoids unnecessary Swift recompilation when generated module map contents have not changed.