fix(pyi): mark union props optional in generated stubs

[benedikt-bartscher]

_get_type_hint returned early for a union annotation and dropped the | None the caller asked for, so a prop declared as a union got a stub signature whose default contradicts its type:

content: Component | Var[str] | str = None

A non-union prop already went through the is_optional branch at the end of the function and came out as Var[bool] | bool | None, so this only ever hit props annotated as an explicit union — HighLevelTooltip.content, HighLevelAccordion.items and Badge.color_scheme today. Type checkers flag the generated signature itself; running pyright over the packages reports five reportArgumentType errors that no source change can fix.

Honour is_optional in both union branches (typed and string annotations). Only markdown.pyi changes among the tracked stubs.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge with no actionable correctness, security, or repository-rule issues identified.

Summary

• Updates both runtime and string-annotation union handling.
• Adds focused regression tests for optional union rendering.
• Adds a representative component fixture and updates its golden stub.
• Refreshes the generated-stub hash and package news fragments.

_{Reviews (2) · Last reviewed commit: "Merge remote-tracking branch 'upstream/m..."}

[codspeed-hq]

Merging this PR will not alter performance

✅ 40 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing benedikt-bartscher:fix-pyi-union-prop-optional (0b3af79) with main (9165dc6)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cubic-dev-ai]

No issues found across 7 files

_{Re-trigger cubic}