Fixed runtime crashes when static xcframeworks are wrapped by dynamic xcframeworks

Tuist no longer relinks static xcframeworks that are absorbed by a dynamic xcframework when using cache warming. Instead, it exposes them through framework search paths, which gives the consumer compile-time module visibility without duplicating symbols at link time. This resolves runtime crashes caused by duplicated symbols and double registration for libraries with global state, such as Firebase, while still letting imports resolve correctly.