Warm test builds stay incremental when dependency module maps are generated

Previously, generated dependency module maps and framework search path response files were rewritten on every generation, which updated their modification time and invalidated Swift compilation. Tuist now skips rewriting unchanged generated files and preserves active compiler inputs across warm tuist test –build-only runs.