Fix #25575: derive generichost TokenProvider deps from per-operation auth
Fixes #25575
With an apiKey scheme declared, every generichost Api class took TokenProvider<ApiKeyToken> in its constructor even when none of its operations used that scheme, breaking DI resolution for the others. The class-level TokenProvider blocks now key off per-class flags computed from the operations' own auth methods (webhook Api classes included), instead of the global scheme presence. Support files (ClientUtils, RateLimitProvider) are untouched.
All 51 generichost samples regenerated (129 Api/*.cs files, removals only); dotnet build on sdk:8.0 passes for the issue repro, a mixed-scheme client, and the petstore sample; *CSharp generator test suite 104/104 with a new regression test + fixture.
Summary by cubic
Fixes #25575: generichost Api classes now only inject TokenProvider dependencies for security schemes their operations actually use, instead of always requiring them when a scheme is declared anywhere.
- Previously, any Api class took
TokenProvider<ApiKeyToken>in its constructor whenever the spec declared anapiKeyscheme, even if none of its operations used it, breaking DI resolution for those classes. - Token provider flags are now computed per class from the operations' own auth methods (webhook Api classes included).
- Support files (
ClientUtils,RateLimitProvider) are untouched, and a regression test with a fixture was added.