From Cloud to Scale

[pepicrft]

Short description 📝

I'm renaming cloud to scale because it's more representative of what the features that require a server are for: scaling up projects. Reached a point where the project is large, developers need things like faster builds, or insights from their projects to be able to make informed decisions. That's where tuist scale will pay an important role.

Implementation 👩‍💻👨‍💻

• Rename all uses of cloud in the codebase to scale.
• As part of this PR I'm also adding analytics through Segment in order to understand how users use the website and optimize it for a better experience navigating and finding content. By law this requires a cookies and privacy policy that I also included in the website.
• Improved the warm-cache logic to work even if the scale configuration is not passed. Frameworks are cached locally in that case.
• Improve the graph cache mapper to tree-shake the projects and delete the schemes whose targets have been turned into .xcframeworks.

[andreacipriani]

The changes are good. But as you know from our chat, I think that cloud is more understandable in this context than scale