This version fixes a runtime crash that could occur when a dynamic XCFramework cached by Tuist absorbed a static XCFramework, such as Firebase wrapped behind a dynamic Analytics facade.
Previously, Tuist relinked the absorbed static XCFramework at the consumer target level. That duplicated symbols from libraries with global state and caused crashes when singletons or Objective-C classes were registered more than once. The dynamic XCFramework already re-exports those symbols, so the extra link was unnecessary.
Now, Tuist exposes the static XCFramework through framework search paths instead of adding it to the link phase. This keeps the module visible at compile time so imports resolve, while eliminating the duplicate symbols and runtime crashes.