[WOOMOB-3739] Cut Product Detail over to Compose (3/3)

[hichamboushaba]

Description

Stack: #16393 → #16394 → this PR. Review after #16394; part 3 of 3.

Note

The important thing for now is to get the screen to Compose, as this would make aligning any small changes later easier. And because of this please note two things:

• We are keeping all the old icons for now, I'm discussing using new icons with the designer, and will update them in a follow up PR.
• The screen is not fully migrated to Compose, I will migrate the gallery header to Compose in a follow up PR.

Fixes WOOMOB-3739.

This is part 3 of 3 in the Product Detail Compose migration stack. It cuts both Add and Edit Product Detail over to the shared renderer while retaining the Fragment-owned XML shell for navigation, dialogs, results, analytics, the toolbar/menu, two-pane coordination, and the collapsing image gallery.

The Compose body owns image-state presentation and property cards. Add More remains fixed outside Coordinator scrolling. Clean public products show icon-only outlined Share and overflow actions; Save or Publish keeps runtime priority and moves Share into the titled overflow row. The XML menu intentionally declares Share as never promoted so reinflation is safe, while ProductDetailsToolbarHelper remains the runtime authority.

The final commit removes the superseded Product Detail promo renderer and skeleton layout. No release-note entry is added because this stack targets the migration feature branch rather than the release branch.

Test Steps

1. Open a clean public product and verify the centered toolbar, outlined Share and overflow actions, fixed Add More footer, and gallery collapse/expand behavior.
2. Scroll through the cards and verify row ordering, inset dividers, Description/Write with AI grouping, neutral AI attribution text, inline review rating, and accessibility labels.
3. Edit the title and verify Save takes priority while Share moves into overflow; discard the edit and confirm direct Share returns.
4. Open Add Product and verify the same Compose renderer handles empty image/title/description/price states, the footer stays fixed, Share is hidden, and exiting does not create a product.
5. Repeat the core flow in landscape and confirm there is no crash, ANR, or Product Detail exception.

Images/gif

Flow	Top	Scrolled
Existing product
Add product

• I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

[dangermattic]

	1 Error
🚫	This PR is tagged with status: do not merge label(s).

	1 Warning
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

	1 Message
📖	This PR contains changes to Tracks-related logic. Please ensure (author and reviewer) the following are completed: The tracks events must be validated in the Tracks system. Verify the internal Tracks spreadsheet has also been updated. Please consider registering any new events. The PR must be assigned the category: tracks label.

Generated by 🚫 Danger

[wpmobilebot]

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

	App Name	WooCommerce Android
	Platform	📱 Mobile
	Flavor	Jalapeno
	Build Type	Debug
	Build Number	778
	Version	25.4-rc-1
	Application ID	com.woocommerce.android.prealpha
	Commit	99f586c
	Installation URL	2vpg9g3e92r90

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

[claude]

AI Code Review - No issues found. The changes look good.

This migrates Product Detail from XML/RecyclerView to Compose (ComposeView hosts for the header, footer, cards list, and upload-error). The state wiring in ProductDetailFragment is consistent across the observers and the updateImagePresentation() / updateProductDetailScreen() derivations, the showShareOptionAsActionWithText -> showShareOptionAsAction rename is confined to the internal MenuButtonsState (no public/backwards-compat surface), and the toolbar navigation refactor adds a proper accessibility content description with a test that verifies stale labels are cleared when navigation is removed. Nice test coverage for the share-as-action vs overflow analytics source.

I checked the one thing that looked like a possible regression — removing the manual LIST_STATE_KEY / onSaveInstanceState scroll restoration — and it is safe: ProductDetailScreen uses rememberLazyListState(), which is Saver-backed, so scroll position is still preserved across configuration changes.

PR housekeeping

• Behaviour-preserving UI refactor (XML -> Compose); no test-plan readiness flag required.
• Applied repo AGENTS.md / CLAUDE.md guidance (store-management MVVM + Compose-in-Fragment patterns) when reviewing.

---

_{Automatic review · claude-opus-4-8 · Workflow run}

_{How to reply to a finding}

Reply on this review (or inline at the line the finding refers to) with one of:

• @claude addressed - I made the change. Bot verifies against the next diff before marking resolved.
• @claude rejected: <reason> - Will not fix; reason gets quoted on the next review.
• @claude not-applicable - Finding does not apply (wrong file, already covered elsewhere, etc.).

The bot honours these on the next review pass.