Fix typed global options DI binding

[carldebilly]

Summary

Closes #23.

Fixes UseGlobalOptions<T>() handler binding when the handler parameter type is the registered global-options type and the parameter name matches a global option name.

The registered typed global-options class is now treated as an implicit DI parameter during command schema generation and runtime binding, instead of being interpreted as a command option or positional argument.

Changes

• Track implicit service-bound parameter types through a shared internal registry.
• Skip typed global-options parameters and framework services, including IGlobalOptionsAccessor, when building command option schemas and documentation.
• Resolve typed global-options parameters from DI during handler binding, including implemented interface/base-class handler parameter types.
• Reject [ReplOption] and [ReplArgument] on typed global-options handler parameters with a clear registration-time error.
• Improve diagnostics for missing typed global-options DI registrations and duplicate typed global-options property names.
• Remove the nullable capturedParsing! path and cache typed global-options property reflection metadata.
• Preserve the existing validation for real global/command option collisions, such as string tenant alongside a global --tenant.

TDD

Added regression coverage for:

• the original ambiguous --tenant failure;
• typed global-options parameters whose handler type is an implemented interface;
• [ReplOption] / [ReplArgument] misuse on typed global-options parameters;
• missing typed global-options DI registration diagnostics;
• duplicate typed global-options property-name diagnostics;
• IGlobalOptionsAccessor not leaking as a --globals command option in help or docs.

Each new behavioral case was run red first, then green after the fix.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.