feat!: Update hyphenation tokens

[VincentSmedinga]

Describe the pull request

Thank you for contributing to the project!
Please use this template to help us handle your PR smoothly.

What

1. Moves the hyphenate-limit-chars token into the typography group.
2. Removes the tokens for hyphens and overflow-wrap
3. Updates docs

Why

1. Because it fits there.
2. Because these values aren’t intended to be customized.

How

n/a

Checklist

Before submitting your pull request, please ensure you have done the following. Check each checkmark if you have done so or if it wasn't necessary:

• Add or update unit tests
• Add or update documentation
• Add or update stories
• Add or update exports in index.* files
• Start the PR title with a Conventional Commit prefix, as explained here.

Additional notes

• n/a

[dlnr]

Makes sense. Also, text-wrap: pretty is something to consider, it will prevent multiple lines that end in hyphens (which is ugly): https://developer.chrome.com/blog/css-text-wrap-pretty

[VincentSmedinga]

Also, text-wrap: pretty is something to consider, it will prevent multiple lines that end in hyphens (which is ugly)

We have already reduced the chance of successive hyphens by only breaking words of at least 12 characters long. Pretty text wrapping still has a performance penalty, so I think hyphenate-limit-chars (which is just landing in Firefox, while Chrome and Edge already support it) should suffice:

Note that pretty has a negative effect on performance, so it should be only used for longer blocks of text when the layout is more important than speed. – MDN