Fix trash product button visibility on tablets

[AdamGrzybkowski]

WOOMOB-1484

Description

While fixing a bug related to the Trash product button visibility (#14657) I introduced this bug where the trash button is not visible in the split pane layout.

This PR adds an additional check to make sure it's enabled in split pane even if the product list is not in the backstack.

Steps to reproduce

1. Open the app on tablet
2. Go to products
3. Tap on the ... menu button
4. Verify the Trash product is visible

Testing information

The above plus:

Using a tablet
2. Go to order
3. Tap on a product
4. Verify the Trash product is gone

Using a phone

1. Go to products
2. Tap on a product
3. Tap on the ... menu button
4. Verify the Trash product is visible

The tests that have been performed

The above

Images/gif

Before	After

• 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.

[Copilot]

Pull Request Overview

This PR fixes a bug where the "Trash product" button was not visible in split pane layout on tablets. The fix adds logic to check if the product detail view is displayed in a detail pane, enabling the trash button even when the product list is not in the backstack.

• Updated the trash button visibility logic to account for tablet split pane layout
• Added a check for detail pane context to enable trash functionality in two-pane mode

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Consider using safe call operator for parentFragment property access. While the logic may be correct in this context, using parentFragment?.id followed by direct comparison could potentially lead to unexpected behavior if parentFragment is null. Consider parentFragment?.id == R.id.detail_nav_container ?: false or restructure the condition to be more explicit about null handling.

Suggested change

	requireContext().isTwoPanesShouldBeUsed && (parentFragment?.id == R.id.detail_nav_container)
	requireContext().isTwoPanesShouldBeUsed && ((parentFragment?.id == R.id.detail_nav_container) ?: false)

[wpmobilebot]

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

	App Name	WooCommerce-Wear Android
	Platform	⌚️ Wear OS
	Flavor	Jalapeno
	Build Type	Debug
	Commit	8bb2dbd
	Direct Download	woocommerce-wear-prototype-build-pr14734-8bb2dbd.apk

[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
	Commit	8bb2dbd
	Direct Download	woocommerce-prototype-build-pr14734-8bb2dbd.apk

[hichamboushaba]

Looks good, thanks for working on this @AdamGrzybkowski, and sorry for missing it too in my review of the previous PR 😅

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.43%. Comparing base (01217d7) to head (8bb2dbd).

Additional details and impacted files

@@            Coverage Diff            @@
##              trunk   #14734   +/-   ##
=========================================
  Coverage     38.43%   38.43%           
- Complexity     9895     9896    +1     
=========================================
  Files          2109     2109           
  Lines        117106   117106           
  Branches      15657    15657           
=========================================
+ Hits          45013    45015    +2     
+ Misses        67921    67920    -1     
+ Partials       4172     4171    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.