Migrate NewDomainsSearchRepository from FluxC to wordpress-rs

[oguzkocer]

Description

Replace FluxC's ProductsStore + dispatcher-based domain suggestions with direct wordpress-rs API calls:

• Fetch domain suggestions via WpComApiClient.domains().suggestions()
• Fetch products via WpComApiClient.products().list() for sale pricing
• Match suggestions to products by productId to get server-formatted combinedSaleCostDisplay (1:1 with trunk's behavior)
• Remove SuggestedDomainsFetcher (FluxC dispatcher wrapper)

Testing instructions

• Compare the Me > Domains > Find a domain flow before and after this change.

Here are 2 recordings to showcase it:
before.webm
after.webm

[dangermattic]

	1 Warning
⚠️	This PR is assigned to the milestone 26.8. The due date for this milestone has already passed. Please assign it to a milestone with a later deadline or check whether the release for this milestone has already been finished.

Generated by 🚫 Danger

[wpmobilebot]

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

	App Name	WordPress Android
	Build Type	Debug
	Version	pr22891-0b11406
	Build Number	1488
	Application ID	org.wordpress.android.prealpha
	Commit	0b11406
	Installation URL	4iq9lhi4fgrdg

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

[wpmobilebot]

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

	App Name	Jetpack Android
	Build Type	Debug
	Version	pr22891-0b11406
	Build Number	1488
	Application ID	com.jetpack.android.prealpha
	Commit	0b11406
	Installation URL	77580pnd0paag

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

[wpmobilebot]

🤖 Build Failure Analysis

This build has failures. Claude has analyzed them - check the build annotations for details.

[oguzkocer]

@jkmassel Would you prefer if we changed these parameter field names to comply with our checkstyle rules, or keep them as is — matching what the API returns?

[jkmassel]

I think it makes a lot more sense to match the API

[codecov]

Codecov Report

❌ Patch coverage is 95.12195% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 37.32%. Comparing base (fc05d3b) to head (0b11406).

Files with missing lines	Patch %	Lines
...earch/domainsfetcher/NewDomainsSearchRepository.kt	95.12%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##            trunk   #22891   +/-   ##
=======================================
  Coverage   37.32%   37.32%           
=======================================
  Files        2320     2319    -1     
  Lines      124578   124583    +5     
  Branches    16926    16928    +2     
=======================================
+ Hits        46498    46506    +8     
+ Misses      74319    74316    -3     
  Partials     3761     3761           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.