Fix paid requests localization

[d-alleyne]

Fixes Automattic/i18n-issues#853

Proposed changes:

• Updates the Jetpack Search features table to use the user's locale for number formatting.
• This change replaces hardcoded 'en-US' locales with the user's locale for better internationalization support.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

1. Check out the branch with the changes.
2. Set the user's locale to Japanese.
3. Navigate to the Jetpack Search screen (/wp-admin/admin.php?page=jetpack-search) and view the Features table.
4. Verify that the number of records and requests is correctly formatted based on the user's locale. Specifically, 1万 is present.

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the fix/paid-requests-localization branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack fix/paid-requests-localization
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[kangzj]

It tests well for self hosted!

Jetpack Search dashboard fails to load on trunk for Atomic. For awareness @ice9js @jeherve. I had a look - the assets don't seem to be loaded 🤔

More info: p1724102580150579-slack-C02ME06LF

[jsnmoon]

These changes appear reasonable and work well on my self-hosted, simple, and atomic test sites:

Self-hosted

Simple

Atomic

Testing on Atomic was interesting. Currently, it's only possible to move a Dotcom site to the Atomic infra by purchasing a Business plan (which includes Jetpack Search classic), changing the host to wpcomstaging.com (via plugin install or hosting config panel), and then manually removing the business upgrade from the site.

[jsnmoon]

We appear to internationalize number formatting in two ways in this file:

1. Using Intl.NumberFormat as shown in this PR.
2. Using __ as shown in line 313: __( '5k records', 'jetpack-search-pkg' ).

We should simplify this and use a single internationalization approach in a future PR.