Fix archive failures caused by redundant module map copies in static frameworks

Apps that depend on static Objective-C frameworks backed by Swift package products no longer fail during xcodebuild archive with errors like “Umbrella for module ‘…’ already covers this directory”. Tuist was previously copying the module map into static framework products as part of the dependency handling introduced in #11135, which created a second module-map entry point for the same umbrella headers and broke clang’s module resolution. The generated project now only copies module maps into dynamic framework products, so dependency module resolution stays intact and the archive succeeds. Dynamic framework behavior is unchanged.