Library products are cached in the module cache

Static and dynamic library targets can now be cached as binary products through the module cache, alongside framework targets. The cache warm step now creates library XCFrameworks with xcodebuild -create-xcframework -library and passes -headers when the source target declares public headers; on restore, Tuist reads the standard HeadersPath metadata and exposes the cached library’s Swift module directories and public header folders to generated targets. Mixed graphs that include reusable library modules no longer have to rebuild those modules from source on every run.