fix(ci): make sdk_swift resolve non-blocking on release PRs

When a release PR bumps PROJECT_VERSION (e.g. to 0.19.8), Package.swift's
binary targets point at release-asset URLs for that not-yet-existing
version, so `swift package resolve` 404s. This blocks release PRs from
ever merging — a chicken-and-egg problem.

Make resolve non-blocking (consistent with swift build below it) so the
job becomes a smoke check rather than a hard gate. The actual binary
validation happens in release.yml once the tag is pushed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: sanchitmonga22

.github/workflows/pr-build.yml

@@ -300,7 +300,11 @@ jobs:
         with:
           platform: ios
       - name: Resolve Swift package
-        run: swift package resolve
+        # Non-blocking: Package.swift points to binaries at the bumped version,
+        # which may not exist yet on a release PR (chicken-and-egg). The
+        # release.yml workflow will produce them. Swift build below is similarly
+        # gated.
+        run: swift package resolve || echo "::warning::swift package resolve failed — binaries at v${PROJECT_VERSION} may not exist yet (ok on release PRs)"
       - name: Build Swift package (smoke check)
         # Builds with whatever Binaries/ already contains (or fetches remote per Package.swift).
         # We don't fail the SDK job if natives aren't present yet — that's a follow-up.