Generated module map mtimes preserved across warm builds

Tuist now keeps the file modification time stable when generated dependency module maps and response files are unchanged, and only deletes stale generated files it owns. This fixes unnecessary Swift recompilation during warm tuist test –build-only runs when generated compiler inputs were rewritten with the same contents.