Publish an official Typer adapter

[codeforester]

Parent: #50

Train position: 11 of 22
Phase: P1 — Incremental adoption

Problem

Typer users currently lack a supported way to adopt the same lifecycle without abandoning Typer-native APIs.

Acceptance criteria

• Supported Typer versions can adopt the lifecycle through an official helper, class, or optional extra.
• Commands, nested apps, help/completion, exceptions, typed parameters, and dependency injection remain Typer-native.
• Lifecycle options, Context access, redaction, and outcomes match the Click integration.
• Compatibility tests and a migration example ship without making Typer a core dependency.

Dependencies

• Attach the lifecycle to existing nested and lazy Click command trees #57
• Make standard lifecycle options independently composable #58
• Publish stable typed runtime, profile, and context extension contracts #59