Dashboard: don't pad money past the currency's own decimals when moneyStrategyPrecision is higher

[julian-boerema]

We run the documented three-decimal MoneyStrategy (precision = 3) with EUR, which has two decimals. Prices at a real third decimal need it. But order totals, payments and refunds settle to whole cents, so every settled amount in the dashboard shows a dead zero: €33.280. When no precision is passed, useLocalFormat().formatCurrency (packages/dashboard/src/lib/hooks/use-local-format.ts) sets both minimumFractionDigits and maximumFractionDigits to moneyStrategyPrecision, and nothing lets you change that.

Proposed default: show the currency's own decimals, and show the store's full precision only when the extra digits are not zero.

• EUR at precision 3: €12.340 → €12.34, while €12.345 stays €12.345
• JPY at precision 2: ¥1,000.00 → ¥1,000, while ¥1,000.50 stays ¥1,000.50

const currencyDigits = new Intl.NumberFormat(locale, { style: 'currency', currency }).resolvedOptions().maximumFractionDigits;
const extraDigits = Math.max(moneyStrategyPrecision - currencyDigits, 0);
const padded = !Number.isInteger(value) || value % 10 ** extraDigits !== 0;
const digits = precision ?? (padded ? moneyStrategyPrecision : Math.min(currencyDigits, moneyStrategyPrecision));
// minimumFractionDigits: digits, maximumFractionDigits: digits

Nothing changes when a caller passes precision (the metrics widget passes 0), or when the store has no decimals beyond the currency's: the default precision 2 with USD or EUR. A currency with more decimals than the store keeps (BHD has 3, the store 2) stays at the store's 2 and is never padded with a zero that isn't stored.