The previous change #191 treated the OSC hyperlink edges as unbreakable, but it still incorrectly broke an OSC hyperlink sequence in half if the hyperlink text also contained spaces.

The most naive approach simply says "nothing ever breaks in a hyperlink", but that means any "long" hyperlink is entirely unbreakable and cannot be wrapped by a word margin, bleeding off the screen or other ill-effect.

To break OSC is complicated. It is necessary to identify and preserve any existing 'id' parameter, or define and generate new unique ones, and to allow wrapping them by closing and re-emitting a new hyperlink sequence of the remaining text, of matching id, at the next line.

From integration and study of downstream uses and needs, as documented in the primary new public API
function, ``porpagate_sgr()``, there is a need to track, set, and reset SGR attributes at the
boundaries of returned lines when using ``wrap()`` and ``clip()``:

A related bug was discovered through extensive testing of "cafe" plus combining character,
that the combining characters were accidentally included outside of clip boundary, confused
with the zero-width nature of SGR codes

Closes #190.

By our cautious use of ``list_versions()`` and other public API's, safely ignore any ``unicode_version`` argument or ``UNICODE_VERSION`` environment variable. No such things are ever processed.

A 20-30% performance boost is found by careful study of ``@lru_cache`` performance quirk, by careful construction of positional-only arguments, of fewest possible positions, in the common case.

This "performance boost" would have worked with multiple version tables too, not necessarily related but a nice discovery made along the way.