Make standard lifecycle options independently composable

[codeforester]

Parent: #50

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

Problem

Every app receives the complete fixed set of lifecycle flags, and group state can overwrite a consumer's typed click.Context.obj.

Acceptance criteria

• Each standard option can be enabled, disabled, renamed, or configured independently while current App defaults remain compatible.
• User-option collisions and incompatible aliases fail at registration with actionable errors.
• Normalized lifecycle values live in a namespaced typed record in click.Context.meta without clobbering obj.
• Group/leaf placement, precedence, and help behavior are deterministic and tested.

Dependencies

• Attach the lifecycle to existing nested and lazy Click command trees #57

[codeforester]

Carryover from #57/#79 review: explicitly bridge attached lifecycle options from Click public-name default_map and runtime main(auto_envvar_prefix=...) values; static prefix handling is only partial today. Also decide/configure attached dry-run semantics while keeping vendor callbacks and destinations collision-safe. These were intentionally deferred to this composition issue rather than compromising identity-preserving attachment.