[WOOMOB-1443] Filter out unsupported products and variations in Local Catalog

[malinajirka]

#WOOMOB-1443

Description

This PR filters out unsupported products and variations in the Local Catalog. Variations were filtered out even before, but they are filtered out on the database layer now.

Testing information

1. Verify downloadable products are not visible in the POS
2. Verify downloadable variation isn't visible in the POS
3. Verify product with non-published status isn't visible in the POS

The tests that have been performed

The above

Images/gif

N/A

• 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 moves product and variation filtering from the application layer to the database layer, ensuring only supported items (published, non-downloadable, simple/variable products) are retrieved from the Local Catalog. This change improves performance by reducing in-memory filtering and ensures consistency across the POS feature.

• Filtering moved from application layer to database queries for products and variations
• Added SQL conditions to filter out unpublished, downloadable, and unsupported product types
• Removed redundant applyFilter() function since filtering now happens at database level

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
WooPosProductsDao.kt	Added SQL filters for status, product type, and downloadable flag to product query
WooPosVariationsDao.kt	Added SQL filters for status and downloadable flag to variation query
WooPosVariationsInDbDataSource.kt	Removed application-layer filtering function now handled by database
WooPosProductsTypesFilterConfig.kt	Added clarifying comment about Local Catalog filtering location

---

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

[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	ee00183
	Direct Download	woocommerce-wear-prototype-build-pr14767-ee00183.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	ee00183
	Direct Download	woocommerce-prototype-build-pr14767-ee00183.apk

[kidinov]

LGTM!

[kidinov]

Seeing the comment, I assume you considered reusing this for the filteriting to have a single source of truth for the whole POS; therefore, just curious why you didn't go with that approach?

[malinajirka]

Good question. I couldn't figure out a way on how to re-use it.

1. We likely want to filter on the DB layer for performance/memory reasons.
2. This config lives in a different module than the DB -> we can't create a circular dependency.
3. Room queries can reference only constants.
   Wdyt? Can you think of a way on how to re-use it?