RunGeometry

[ickshonpe]

Objective

Follow up to the underline and strikethrough PRs:

• Replace the quintuples stored in TextLayoutInfo::section_geometry with a struct with named fields.
• Rename TextLayoutInfo::section_geometry because "section" in our terminology implies a one-to-one correspondence with text entities.
• Add some basic helpers to construct the underline and strikethrough lines.
• Seperate the thickness values for underline and strikethrough. This is needed for an API that allows users to set custom thicknesses.

Solution

• New struct RunGeometry. RunGeometry holds the bounds and decoration geometry for each text run (a contiguous sequence of glyphs on a line that share text attributes). It has helper methods for placing underline and strikethrough.
• Rename the section_geometry field to run_geometry and make it a Vec<RunGeometry>
• RunGeometry has seperate underline_thickness and strikethrough_thickness values.

[alice-i-cecile]

I like the change, but do we need a migration guide? I intend to get this shipped for 0.18, and I'm not sure that the field existed back in 0.17 🤔

[DaAlbrecht]

Yea the migration guide is not needed imo, this field did not exist: https://docs.rs/bevy/latest/bevy/text/struct.TextLayoutInfo.html

[ickshonpe]

I like the change, but do we need a migration guide? I intend to get this shipped for 0.18, and I'm not sure that the field existed back in 0.17 🤔

I think we do a migration guide, but it needs a correction as the field was named section_rects in 0.17

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-21656

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.