More reliable SwiftPM dependency resolution and fewer Package.resolved diffs

Updated Tuist’s internal Swift Package Manager resolution engine, SwifterPM, to resolve dependencies in a separate SwiftPM subprocess instead of inside the main process. This reduces the coupling between the Tuist binary and SwiftPM internals, which should make the tool more stable across SwiftPM changes. The update also fixes two problems reported by users: binary artifacts (for example, the Sparkle xcframework) sometimes failing to download cleanly, and Package.resolved producing unnecessary diffs between runs. As a result, tuist install should be more reliable and commit less unrelated lockfile churn.