Description

This PR enhances proseWrap: "always" to follow Semantic Line Breaks (SemBr), inserting line breaks after [.!?;] characters (where appropriate). This reduces noisy diffs caused by full-paragraph re-wrapping, limiting impact of re-wrapping to (at most) the sentence and making PRs easier to review.

Example diff from before this change (from a GraphQL spec PR):

-Fragments can also be defined inline within a selection set. This is useful for
-conditionally including fields based on a type condition or applying a directive
-to a selection set.
+Fragments can also be defined inline within a _selection set_. This is useful
+for conditionally including fields based on a type condition or applying a
+directive to a selection set.

After this change, only the sentence would be impacted making the changes clearer:

-Fragments can also be defined inline within a selection set.
+Fragments can also be defined inline within a _selection set_.
 This is useful for conditionally including fields based on a type condition or
 applying a directive to a selection set.

hardline upgrades are only used where line was already used, so I think CJK support should be fine?

Checklist

• I’ve added tests to confirm my change works.
• (If changing the API or CLI) I’ve documented the changes I’ve made (in the docs/ directory).
• (If the change is user-facing) I’ve added my changes to changelog_unreleased/*/XXXX.md file following changelog_unreleased/TEMPLATE.md.
• I’ve read the contributing guidelines.

✨Try the playground for this PR✨