Library products can be cached in the module cache

Static and dynamic library targets can now be cached and reused as binary XCFrameworks through the module cache. When warming, Tuist creates library XCFrameworks and preserves the Swift module directories and public headers needed for compilation. Mixed graphs can cache library modules alongside frameworks without forcing them to become frameworks.