DocC builds now work for packages with public headers that import sibling modules

DocC builds for generated projects now succeed for Swift Package targets whose public Objective-C headers import another module from the same package. Tuist derives missing target dependencies from concrete #import/#include references in public headers and copies generated framework module maps to the canonical Modules/module.modulemap location that DocC’s ExtractAPI invocation expects.