[Shipping labels] Remotely validate edited address

[rachelmcr]

Part of: #13781
⚠️ Based on #15020 ⚠️

Description

This adds remote validation to the address editing view in the Woo Shipping label flow.

When the "Validate & Save" button is tapped, it remotely validates the address and opens a sheet to confirm the address. This suggests the normalized address provided by the backend. (Note that we are matching the web behavior and displaying this view even if the entered and suggested addresses match.)

Changes

• In WooShippingEditAddressView:
  • When the status is unverified tapping the primary button now calls the view model's remotelyValidateAddress() method (and shows a loading indicator while the request is in progress).
  • When the view model's normalizeAddressVM is set, it opens a sheet with the normalize address view.
• In WooShippingEditAddressViewModel, we prepare the address to be validated with the current field values, call the remote action, and set normalizeAddressVM based on the response.
• WooShippingNormalizeAddressViewModel is updated to include an ID (so it can be used as a SwiftUI sheet item) and its closure is now optional for convenience.

Notes:

• We don't yet handle an error response from the validation endpoint. For now errors are logged to the console, but a later PR will add them to the UI.
• The full "confirm address" flow isn't finished yet, so the address can't be confirmed after that sheet is opened. That will come in a later PR.

Testing information

1. Ensure the latest production version of WooCommerce Shipping (Version 1.3.2) is installed, activated, and set up on your store.
2. Create or open an order with at least one physical product and the processing status.
3. Tap "Create Shipping Label" in order details.
4. Open the "Shipment details" bottom sheet.
5. Tap the "Ship from" origin address.
6. Tap the edit (pencil) icon on one of the origin addresses.
7. In the edit address sheet, update the name field.
8. Tap "Validate & Save" and confirm the "Confirm Address" sheet opens with the entered and suggested (normalized) address.
9. Tap "Cancel" to go back and enter a non-existent address.
10. Tap "Validate & Save" and confirm the error from the remote endpoint is logged to the console, and the "Confirm Address" sheet does not open.

Screenshots

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-01-30.at.15.31.36.mp4

---

• 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	pr15023-1f11137
	Version	21.5
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	1f11137
	App Center Build	WooCommerce - Prototype Builds #12748

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

[toupper]

LGTM! Just a minor non blocker comment 🚀 🚢

[toupper]

According to the comment, would the property be named isRemotelyValidated instead of validating?

[rachelmcr]

No, this property is like an isLoading property, tracking when the remote validation is in progress (so we can show the loading indicator on the button). I'll update the comment to make that clearer 👍

[toupper]

Awesome, thanks for the clarification

[wpmobilebot]

Version 21.6 has now entered code-freeze, so the milestone of this PR has been updated to 21.7.