Fix DocC builds for package targets with cross-module Objective-C imports

DocC documentation builds now work for generated projects whose Swift package targets have public Objective-C headers that import another module from the same package. Tuist derives missing package target dependencies from public headers and copies generated module maps to the canonical Modules/module.modulemap location that DocC’s ExtractAPI step expects.