Generate projects with the module imports SwiftPM package docs need

DocC builds for generated projects no longer fail when a Swift package target’s public Objective-C headers import another module from the same package. Tuist now derives the missing target dependency from concrete #import/#include references in public headers (only when the referenced module is a regular target in the same package, only when the dependency is not already declared, and only when adding it would not create a cycle). Framework targets also get a build-step copy that publishes the dependency module map at the canonical Modules/module.modulemap path so Clang ExtractAPI can discover framework dependency closure the same way as swift-build.