SwiftPM dependency resolution is more stable

The dependency resolver has been switched to run SwiftPM in a subprocess instead of linking it directly. This reduces the risk of Tuist breaking when SwiftPM’s internal APIs change, and keeps resolution behavior closer to a standard SwiftPM run. You should see fewer unexpected resolution failures across Tuist updates.