Add first-class component glyph views

[kostyafarber]

What changed

• Replace the separate recursive GlyphOutline / render-model path with a first-class GlyphView containing ComponentGlyph and GlyphContour occurrences.
• Make rendering, previews, text layout, bounds, xAdvance, and sidebearings consume the same composed glyph view.
• Keep editing presentation root-owned: component contours render and measure correctly but do not expose parent-glyph point handles.
• Add Rust-owned GlyphComponents relationships with stable component paths, parent/child ancestry, anchor attachments, authored order, and cycle pruning.
• Resolve each component glyph independently at the root location using exact master → interpolation → deterministic master fallback → explicit error.
• Exclude layer-only/background sources from component projection.
• Support sparse one-axis interpolation when compatible component masters bracket a missing default layer.
• Hard-delete the provisional outline/shape/provider abstractions and regenerate bridge types.

Why

Sidebearings were derived from the root glyph's direct geometry. A pure component glyph has no direct contours, so its root bounds were null even though a separate recursive outline path rendered it correctly. This split also required TypeScript to repeat component traversal semantics owned by Rust.

The new model keeps composition, interpolation, and editability orthogonal. Source contour coordinates are shared once per base glyph at the view location; each placement adds only a transform/provenance occurrence wrapper. ComponentGlyph.contours and the flattened GlyphView.contours reference the same occurrence objects.

Impact

Pure and mixed component glyphs now provide composed bounds and sidebearings in the editor sidebar, previews, and text layout. Rust and the renderer share one component occurrence model, including repeated/nested placements and anchor attachment identity.

Validation

• cargo test -p shift-font -p shift-wire — 171 font tests and 6 wire tests passed
• cargo clippy -p shift-font -p shift-wire -p shift-bridge --all-targets
• pnpm lint:check
• pnpm typecheck
• Focused desktop suite — 89 tests passed, including real Homenaje Aacute composed bounds and 20/20 sidebearings
• Pre-commit full suite — 502 tests passed; two unrelated Electron main-process suites could not collect because the secondary worktree lacks a valid Electron binary

[kostyafarber]

use Vec

[kostyafarber]

we are doing this ok_or_else a lot

[kostyafarber]

template is a bad name

[kostyafarber]

perhaps some inline comments might help to understand whats going on here