Module cache now supports library products

Static and dynamic library targets can now be cached as binary XCFrameworks alongside frameworks in the module cache. The cache warm step emits proper -library arguments and includes public headers, and on restore Tuist maps the standard HeadersPath metadata back into header search paths. Mixed framework and library graphs can now reuse the same binary cache pipeline. Swift modules from cached libraries are exposed as include paths to generated targets.