fix(cli): pin SwifterPM revision

What changed

Tuist now temporarily depends on SwifterPM revision 672a723f962cf243f1b6de65274c744c51e82acc instead of the tagged 0.8.3 release.

Package.resolved was updated to reflect that revision pin and the tuist.FileSystem 0.18.0 transitive requirement introduced by the SwifterPM fix.

Why

The current CLI release path needs the SwifterPM change that shells out to SwiftPM and removes the raw SwiftPM library dependency before a tagged SwifterPM release is available. Pinning the revision lets Tuist consume that fix immediately while keeping the change easy to revert once SwifterPM publishes a tag.

Root cause

The Tuist binary regression came from pulling in SwiftPM as a library through SwifterPM, which changed the packaged CLI binary shape and introduced Swift runtime compatibility library expectations on CI. The SwifterPM fix restores a consumable path that avoids inheriting that raw SwiftPM revision dependency.

Impact

This is intentionally temporary. Tuist can unblock the CLI fix now, and we should switch back to a tagged SwifterPM release as soon as one containing the FileSystem/shell-out fix is published.

Validation

• swift package --disable-sandbox --scratch-path /private/tmp/tuist-spm-scratch-672a --cache-path /private/tmp/tuist-spm-cache --config-path .swiftpm/configuration --security-path /private/tmp/tuist-spm-security --manifest-cache local --replace-scm-with-registry --force-resolved-versions resolve
• git diff --check