chore(cli): let SwiftPM own registry transformation via SwifterPM 0.8.10

What changed

Bumps the exact SwifterPM dependency from 0.8.9 to 0.8.10 and refreshes the resolved revision in Package.resolved.

The main improvement from 0.8.10 is that SwifterPM now defers SCM-to-registry transformation to SwiftPM itself, from tuist/swifterpm#38.

Why

Keeping that transformation inside SwiftPM reduces the amount of resolution behavior SwifterPM has to mirror. That should make the opt-in SwifterPM path behave closer to vanilla SwiftPM and avoid divergence around registry replacement and Package.resolved stability.

Impact

Tuist’s TUIST_USE_SWIFTERPM flow picks up the upstream resolver behavior without changing Tuist’s integration code.

Validation

• swift package resolve --replace-scm-with-registry
• tuist generate tuist TuistSupport TuistSupportTests ProjectDescription --no-open
• xcodebuild test -workspace Tuist.xcworkspace -scheme Tuist-Workspace -only-testing TuistSupportTests/SwiftPackageManagerControllerTests CODE_SIGNING_ALLOWED=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY="" COMPILATION_CACHE_ENABLE_CACHING=NO

The targeted test run executed 12 tests with 0 failures.