[Mobile Payments] Handle Network errors for payments using site credentials

[joshheald]

Closes: #14409

Description

This PR ensures that we decode specific payment-related NetworkErrors, which we receive when using site credentials rather than Jetpack.

Additionally, it resolves an issue that was preventing localized error messages from being shown when payment capture failed. Without fixing this, it would be very difficult to test.

Two payment errors are covered: errors fetching a charge, and errors capturing a payment.

Steps to reproduce

To cause an error when fetching a charge, replace the path in WCPayRemote.fetchCharge(for:chargeID:completion:) with:

let path = "\(Path.charges)/\(chargeID.lowercased())"

1. Open the orders tab
2. Select an order paid using WooPayments
3. Tap Issue Refund
4. Observe that the error is shown.
5. With a breakpoint, observe that a call is made to delete the charge from storage: CardPresentPaymentStore.fetchCharge(siteID:chargeID:completion:)

To cause an error when capturing a payment, replace the minimumAllowedChargeAmount in CardPresentPaymentsConfiguration with a lower number, e.g. 0.1, then try to take payment for an amount between the real minimum and your reduced minimum.

1. Open the orders tab
2. Create an order for an amount below the real minimum
3. Tap Collect Payment
4. Tap a card
5. Observe that the descriptive error from the server is shown

Note that this PR does not fully adopt the new error available in WooPayments – pdfdoF-6h1-p2 for context. To do that, we can add to the decoding of the data returned with the error, which will be easier with NetworkError than DotcomError. When we do adopt that, we can provide the localization in the app, rather than relying on the server localization as we do in these cases now.

Testing information

There's no visual difference when refunding a payment, the correct unwrapping of the error triggers a call to delete the charge from storage.

When capturing a payment, you can now see the message from WCPay or the app's localization in the UI, rather than Yosemite.ServerSideCaptureError 0

Screenshots

Capture

Jetpack login

Before	After

Site creds login

Before	After

Refund

Jetpack login

Before	After

Site creds login

Before	After

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Reviewer (or Author, in the case of optional code reviews):

Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement:

• The PR is small and has a clear, single focus, or a valid explanation is provided in the description. If needed, please request to split it into smaller PRs.
• Ensure Adequate Unit Test Coverage: The changes are reasonably covered by unit tests or an explanation is provided in the PR description.
• Manual Testing: The author listed all the tests they ran, including smoke tests when needed (e.g., for refactorings). The reviewer confirmed that the PR works as expected on all devices (phone/tablet) and no regressions are added.

[wpmobilebot]

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

	App Name	WooCommerce iOS
	Build Number	pr14980-14b7bb8
	Version	21.5
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	14b7bb8
	App Center Build	WooCommerce - Prototype Builds #12698

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

[iamgabrielma]

LGTM 🚢

✅ Triggers a call to delete the charge from storage when needed
✅ When failing capturing a payment, the proper localized error appears

TIL that the chargeID is case-sensitive