fix: normalize yaml outputs to always use -1 lineWidth

[JoshuaKGoldberg]

PR Checklist

• Addresses an existing open issue: fixes 🐛 Bug: Long YAML uses with # comment gets printed as multiline string #2097
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Whatever reason I had for having two different calls to jsYaml.dump is, I think, no longer there. This normalizes all YAML printing to go through the standard formatYaml. YAML files now always have a blank line between root-level properties.

🎁

[github-actions]

PR Compliance Checks Passed!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.82%. Comparing base (25e9a51) to head (f1cddef).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2098   +/-   ##
=======================================
  Coverage   99.82%   99.82%           
=======================================
  Files         127      126    -1     
  Lines        5185     5185           
  Branches      357      357           
=======================================
  Hits         5176     5176           
  Misses          9        9           

☔ 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.

[github-actions]

🎉 This is included in version v2.22.2 🎉

The release is available on:

• GitHub releases
• npm package (@latest dist-tag)

Cheers! 📦🚀