[POS UI extensions version 2025-10]: Refine example descriptions, limitations, and links

[mcvinci]

This PR:

• Integrates Tim Trevor's feedback on the following:
  • Refines API example descriptions to avoid long sentences (>30 words), and the participial phrase
  • Removes certain API limitations that shouldn't be called out at that level, using a "Limitations framework"
• Adds some links to cross-reference component docs
• Adds descriptions for recently added POS UI extensions examples
• Closes https://github.com/Shopify/shopify-dev/issues/65493

Limitations framework

• Limitations are constraints developers must work around: I only documented restrictions that require developers to handle edge cases, implement fallbacks, or design around boundaries (like size limits, availability restrictions, or failure conditions).
• Limitations are not product descriptions: I removed statements that simply describe how the product is designed to work, its intended scope, or its normal operating requirements (like "requires hardware" or "provides read-only access").
• Limitations highlight what can go wrong or fail: I focued on technical boundaries where operations can fail, data can be stale, or functionality is conditionally available, rather than explaining the product's standard behavior or architecture.

Tophatting

1. In the ui-extensions repo, run yarn docs:point-of-sale 2025-10.

2. In shopify-dev, run a server (dev server) with the templated_refs_v2_m1 feature flag enabled, and review the 2025-10 docs at https://shopify-dev.shop.dev/docs/api/pos-ui-extensions/2025-10

[github-actions]

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.

[timtrevor-shopify]

See 2026-01 PR for comments on limitations sections of API pages.
Approving pending resolution of those comments.