Build cached nested static Objective-C xcframeworks through their own module map (ARCore)

When a cached static Objective-C xcframework lays out its module map and public headers inside a Headers/<ModuleName>/ subdirectory and the headers re-import each other with the prefixed <Module/Header.h> form (so Google’s ARCore ARCoreGARSession / ARCoreGeospatial and similar), Tuist now consumes such xcframeworks through their own module map and adds the xcframework’s Headers root to the consumer’s header search paths. The module is defined exactly once and the <Module/...> sibling imports resolve, so generating and building tools that depend on these cached static xcframeworks behind a dynamic framework succeeds instead of failing with “file not found” or “import of shadowed module” errors.