More stable Swift Package Manager resolution with fewer Package.resolved changes

Updated the bundled SwifterPM dependency so that package resolution now runs in a separate SwiftPM subprocess. This fixes cases where binary artifacts (such as Sparkle’s xcframework) could fail to download depending on the cache state, and it reduces unnecessary churn in Package.resolved between runs, so your lockfile stays more stable and dependency installs are more reliable.