Cache static and dynamic library targets in the module cache

Projects using static or dynamic library targets can now reuse module cache binaries across local and CI builds. Previously, only framework products were cached as binary XCFrameworks, so library targets had to rebuild from source even when their graph could otherwise be restored from cache. Tuist now creates library XCFrameworks during cache warm and restores the Swift module directories and public headers needed to compile against them.