Package documentation builds resolve cross-module imports from public headers

For package manifests where target dependencies come from concrete #import/#include references in public headers rather than declared Package.swift dependencies (such as Firebase), Tuist now adds the missing build dependency boundary and copy the dependency framework’s module map to Modules/module.modulemap so that DocC’s ExtractAPI invocation can resolve cross-module imports. DocC builds for generated projects with these packages now succeed.