Static frameworks no longer get a copied module map

Tuist no longer copies module maps into static framework products while leaving dynamic framework behavior unchanged. The earlier copy applied to both .framework and .staticFramework because it checked target.product.isFramework, and the duplicate module map caused clang to fail archives of ObjC static frameworks that imports sibling headers via <Module/Header.h> with Umbrella for module 'X' already covers this directory. The mapper now gates the copy phase on target.product == .framework so static frameworks rely on the existing dependency module map only.