DocC builds work for package header module imports

DocC builds for generated projects now succeed for packages whose public headers import another module from the same package that is not explicitly declared as a target dependency, such as FirebaseCoreExtension importing FirebaseCore. Tuist mirrors upstream behavior by generating the missing build edge from public header imports and by copying dependency module maps to the canonical Modules/module.modulemap location that DocC’s ExtractAPI invocation expects.