fix(formatter): Use hard_space for as_or_satisfies

[leaysgur]

The same as #20858, but for as and satisfies.

Theoretically, there may be other cases where this has an impact, but I haven't been able to find any existing tests that demonstrate it.

[leaysgur]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(formatter): Use hard_space for as_or_satisfies #20859 👈 (View in Graphite)
• fix(formatter): Use hard_space between : and TSTypeAnnotation #20858
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

Merging this PR will not alter performance

✅ 44 untouched benchmarks
⏩ 12 skipped benchmarks¹

---

_{Comparing 03-30-fix_formatter_use_hard_space_for_as_or_satisfies (0a84847) with 03-30-fix_formatter_place_decorator_on_own_line_with_long_property (02ca7b3)}

Footnotes

1. 12 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

prettier/prettier#18148

[Dunqing]

I just remembered this is a upstream bug, see prettier/prettier#18148