Too many text-wrap features

[foolip]

There are 7 features related to text-wrap:
https://webstatus.dev/?q=text-wrap

I think these are inarguably worth describing as standalone features, with distinct use cases:

• text-wrap: balance
• text-wrap: pretty
• text-wrap: stable

I don't think these properties without a value should be features if we keep the more specific features like text-wrap: balance:

• text-wrap
• text-wrap-mode
• text-wrap-style

I'm not totally sure about text-wrap: nowrap.

At some point in the future these features might all just merge into a single text-wrap feature, but not right now I think.

cc @lilles who pointed this situation out to me.

[jamesnw]

I'm not opposed to combining these. My memory is we settled on this feature set based on the support story over the developer story, but it's definitely not a cohesive set.

[foolip]

Since I filed this issue I learned from @kojiishi that text-wrap: stable isn't actually a new capability, but just the default behavior in most browsers given a name. So I don't think that deserves its own feature, only text-wrap: balance and text-wrap: pretty do, in addition to a text-wrap feature for everything else.

My hope is that eventually we would fold all of it into text-wrap, when enough time has passed and we have ways to represent "feature evolution" of that sort.

[foolip]

I've sent #2900 with what I think we should do.