feat: Enable fraction digit formatting for SEO's product:price:amount meta tag

[hellofanny]

What's the purpose of this pull request?

With these changes, merchants will be able to choose the the minimum price fraction digits to be used on SEO's product price meta tag, preventing mismatch values between displayed product price and SEO's product:price:amount.

How to test it?

Check if the displayed price for any product matches with the SEO's product:price:amount meta tag.

Starters Deploy Preview

Summary by CodeRabbit

• New Features
  • Product price meta tags (used by search engines and social previews) now support configurable decimal precision, producing consistently formatted price values for improved SEO and display.
  • When no precision is set, prices fall back to previous default formatting to preserve existing behavior.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Adds seo.pdp.minPriceAmountFractionDigits to default config and uses it to conditionally format the product price metatag (via toFixed) on the PDP; also includes a minor import reordering.

Changes

Cohort / File(s)	Summary
Config packages/core/discovery.config.default.js	Added seo.pdp.minPriceAmountFractionDigits: undefined to exported configuration.
PDP page packages/core/src/pages/[slug]/p.tsx	Compute productPriceAmountMetatag from product.offers.lowPrice; if pdpSeo.minPriceAmountFractionDigits is a number use toFixed(...), otherwise use toString(). Reordered import: getComponentKey moved within imports.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

✨ A tiny config to guide the cents,
Decimals trimmed with prudent sense,
Meta tags neat, the price aligns,
A small tweak humming in the lines.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: enabling fraction digit formatting for the SEO product:price:amount meta tag, which directly aligns with the changeset's core functionality.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@packages/core/src/pages/`[slug]/p.tsx:
- Around line 109-118: The current guard treats 0 as falsy and may pass an
out-of-range value to Number.prototype.toFixed, causing SSR errors; update the
check around productPriceAmountMetatag to allow product.offers.lowPrice === 0 by
testing for lowPrice != null and to validate pdpSeo.minPriceFractionDigits with
typeof === 'number' and clamp it to the safe toFixed range (0–20) before calling
toFixed (or skip formatting if the number is out of range), referencing
productPriceAmountMetatag, product.offers.lowPrice,
pdpSeo.minPriceFractionDigits and the toFixed call so the formatted string is
produced safely.

[eduardoformiga]

Do we need to ask the education team to document this new option?

[hellofanny]

nice!
Just to emphasize I think we should be using default and the usage of this prop is in a very specific context (customization of the schema, we could add this note and scenario in the doc to be clear)