[Shipping Labels] Load order destination address from remote

[selanthiraiyan]

Closes: #15176

Description

Loads the order destination address and the verification status from the remote.

Changes

• Make isTrivialNormalization property optional as remote will send it only when the address is not already verified.
• Load the order destination address and status from remote. If destination address is not found fall back to the shipping address of the order.
• Make destinationAddressStatus property optional in view model to wait until we load the value from the remote.
• Unit tests.

Steps to reproduce

Prerequisite: WooCommerce Shipping is installed, activated, and set up on your store.

Missing address

1. Create or open an order with at least one physical product and the processing status and no shipping address.
2. Tap "Create Shipping Label" in order details.
3. Validate that you see a notice that "Destination address is missing"

Unverified address

1. Create or open an order with at least one physical product and the processing status, and a shipping address.
2. Tap "Create Shipping Label" in order details.
3. Validate that you see a notice that "Destination address unverified"

Verified address

1. Create or open an order with at least one physical product and the processing status, and a shipping address.
2. Open the order from wp-admin and open the shipping label creation flow.
3. Tap on the destination address and follow the steps to verify it.
4. Open the order from the mobile app.
5. Tap "Create Shipping Label" in order details.
6. Validate that you see a notice that "Verified destination address"

Testing information

Screenshots

Missing	Unverified	Verified

---

• 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	pr15250-26de3f0
	Version	21.8
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	26de3f0
	App Center Build	WooCommerce - Prototype Builds #13162

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

[rachelmcr]

LGTM! 🚀

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.