Bump wordpress-rs to a build exposing unified support conversations

[adalpari]

Why this is needed

We're porting the Android unified "Get help" support flow (WordPress-Android#22946, #23011) to iOS. That flow merges the separate "Ask the Bots" and "Ask the Happiness Engineers" features into a single combined conversations list + type‑branched detail, backed by a new server‑side combined endpoint in wordpress-rs.

iOS today pins wordpress-rs 0.3.0, which only exposes the separate executors:

• supportBots — bot chats
• supportTickets — HE tickets
• supportEligibility

It does not expose the combined unifiedConversations executor (list / detail / reply for both conversation types) that the whole unification is built on. That endpoint was added in wordpress-rs#1288 ("Add unified support conversations endpoints") — the same rs change Android adopted (1288-85a8554). Without this bump the iOS port is blocked.

What changed

Repins wordpress-rs from exact: "0.3.0" to branch: "pr-build/1414" in Modules/Package.swift + Modules/Package.resolved.

pr-build/1414 is the first SPM‑consumable wordpress-rs build that includes the unified endpoints. The endpoint landed on trunk, but trunk's Package.swift is configured .local (it expects a locally‑built Rust xcframework, which iOS has no tooling to produce), and every existing release tag predates #1288. The pr-build/<PR#> branches are .release‑configured against a prebuilt xcframework published to the CDN, so SPM can download the binary — exactly the mechanism used previously in integrate/wordpress-rs-pr-1367. pr-build/1414's only delta over trunk is an unrelated dependabot CI bump that doesn't touch the Swift/Rust surface.

Verification

• swift package resolve succeeds and downloads …/wordpress-rs/pr-builds/1414/libwordpressFFI.xcframework.zip from the CDN.
• The public client surface (WPComApiClient.swift) diff from 0.3.0 → pr-build/1414 is purely additive — it only adds the unifiedConversations executor; the existing supportBots / supportTickets / supportEligibility / me executors the app already uses are unchanged. So the bump is expected to be non‑breaking for current call sites.
• Full app build/test verification is left to CI.

⚠️ Interim pin — must move to a tagged release before shipping

This is an interim pr-build pin, not a stable release. Before the unified‑support feature ships, wordpress-rs needs to cut a tagged release that includes the #1288 unified endpoints, and this dependency should be repinned to that tag (the iOS equivalent of the "move to a tagged release before merge" caveat from the Android PR). pr-build/* branches are not guaranteed to be permanent.

🤖 Generated with Claude Code

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Configuration	Release-Alpha
	Build Number	32934
	Version	PR #25719
	Bundle ID	org.wordpress.alpha
	Commit	f6eac56
	Installation URL	4e1ngncej9ano

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Configuration	Release-Alpha
	Build Number	32934
	Version	PR #25719
	Bundle ID	com.jetpack.alpha
	Commit	f6eac56
	Installation URL	03j7je7dqom7o

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[crazytonyli]

We can't merge this since the branch goes away after the PR is merged.