ARCore-style xcframeworks now build through the cache

A series of interconnected fixes restores the cached-build path for precompiled xcframeworks with module maps. Targets depending on a module-map xcframework were failing with Redefinition of module in 4.201.0-rc.1; the cache path now excludes those headers for module-map xcframeworks while still adding the xcframework Headers root for the cached static-objc-behind-dynamic case. For ARCore’s nested layout (module map and headers under Headers//, with prefixed sibling imports), Tuist now consumes the xcframework through its own module map so the module is defined exactly once and prefixed imports resolve. Customers who could not cache ARCore (and similarly-shaped Google SDK xcframeworks) can now do so.