fix(yaml): quote leading-zero integer-shaped strings in stringify

[LeSingh1]

Fixes #7040.

resolveYamlInteger accepts "07" as octal so stringify already quoted it, but "08" and "09" fell through because they aren't valid octal:

import { stringify } from "jsr:@std/yaml";
stringify("07"); // "'07'\n"  ok
stringify("08"); // "08\n"    looks like a number
stringify("09"); // "09\n"    looks like a number

These still read as numbers to humans and to other YAML parsers, so they should be quoted too. The fix adds a /^[-+]?0[0-9]+$/ guard in chooseScalarStyle so any integer-shaped string with a leading zero forces single-quoted style. After the patch:

"08"   -> "'08'\n"
"09"   -> "'09'\n"
"089"  -> "'089'\n"
"-08"  -> "'-08'\n"
"0a8"  -> "0a8\n"   (unchanged, not integer-shaped)

Tests added in yaml/stringify_test.ts cover the issue cases plus edge cases (signed, mixed digits, non-integer-shaped strings).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.57%. Comparing base (cdf74a8) to head (06cc8f2).
⚠️ Report is 18 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7164      +/-   ##
==========================================
- Coverage   94.57%   94.57%   -0.01%     
==========================================
  Files         636      636              
  Lines       52142    52144       +2     
  Branches     9401     9402       +1     
==========================================
+ Hits        49315    49316       +1     
  Misses       2249     2249              
- Partials      578      579       +1     

☔ View full report in Codecov by Harness.
📢 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.

[bartlomieju]

Fix looks correct and is at the right layer (verified locally: round-trips clean, deno test -A yaml/ 90/90, fmt+lint clean). Just two non-blocking notes inline.

[bartlomieju]

Non-blocking: the same cross-parser ambiguity exists for other leading-zero number shapes this regex doesn't cover. On this branch these still emit plain:

• 08.5 -> 08.5 (a YAML 1.2 parser reads this as the float 8.5 -- the direct float analogue of the bug being fixed here)
• 0o7 -> 0o7 (YAML 1.2 octal -> 7)

These are arguably out of scope for #7040 (which is specifically leading-zero integers), so no need to expand the fix here -- but worth a one-line note in the PR description or a follow-up issue so it isn't assumed that all leading-zero numeric strings are now safe.

[bartlomieju]

Two small suggestions (optional):

1. Consider also asserting the round-trip directly, e.g. assertEquals(parse(stringify("08")), "08"). That's the actual contract this fix protects (verified it holds), and it guards against future parser changes.
2. Given the 08.5 / 0o7 gaps noted on the regex, the name "quotes leading-zero numeric strings" slightly overstates scope -- "...leading-zero integer-shaped strings" matches what the regex actually covers.