[Woo POS] Hide cart images when the view is too narrow

[joshheald]

Description

This PR adds a minimum width criteria for showing the images on CartItems, as they are often shown in a fairly constrained width, especially in portrait or landscape 2/3rds views.

1/2 landscape view on a 13" iPad never shows images – it's pretty rough even at the smallest sizes if we show them, at least when there's a remove button shown as well. On the Checkout screen it looks like there's space, but it's strange for the cart items to change as you move between those two screens.

The dynamicTypeSize and width go together to decide whether the images should be shown, so the minimum width changes depending on your current type size.

Note that I chose to do the calculations on the cart, not each image. It just felt bad for performance to have lots of views using geometry readers to calculate the exact same answer... but it would be nicer from a code-readability perspective to have it on the item cards.

Another nice step would be to update DynamicHStack to respond to width constraints as well – at the moment, moving to an accessibilty size avoids the Cart title having to wrap, but we could do that at smaller sizes when in a narrower display mode. I think that should be done separately though.

Steps to reproduce

1. Launch the app and navigate to POS
2. Add an item to the cart
3. Observe that at 100% text size (and some sizes above) in landscape fullscreen, the cart image is shown.
4. Navigate to the checkout
5. Observe that the cart image is still shown (or hidden) as it was on the previous screen.

Explore different screen size splits, orientations, and dynamic type sizes.

Testing information

I've tested this by moving between the item list and checkout, in portrait, landscape 2/3rds, and landscape views.

I used an iPad Air on 17.5, an iPad mini simulator, and an iPad Air 13" simulator.

Screenshots

remove.image.in.split.view.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	pr15028-c846d96
	Version	21.5
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	c846d96
	App Center Build	WooCommerce - Prototype Builds #12746

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