Parse inline endpoint response schemas

[Smaug123]

Splits out the first of six fixes from #540 (stack: this ← #543 ← #544 ← #545 ← #546; see also the independent capturing-mock fix).

Endpoint responses fed the whole Response Object to Definition.Parse, so an inline {description, schema} response has neither $ref nor a top-level type and degraded to Definition.Unspecified, generating Task<unit> clients that silently discard the body. Responses now go through Response.Parse (moved above SwaggerEndpoint) and use its schema; $ref responses are handled as before.

Making those schemas parse exposed a second gap: inline schemas under paths were never fed through defnToType, so renderType crashed on anonymous inline objects. Endpoint response and parameter schemas are now seeded into type generation (with no handle name); previously, inline parameter types only rendered when they happened to collide with an identically-shaped named definition in the cache.

Gitea's /users/search, /orgs/{org}/teams/search, and the two signing-key.gpg endpoints now return real types (Type9/Type10/string) instead of Task<unit>.

Test was written first and observed failing: the inline 200 response parsed as Unspecified.

🤖 Generated with Claude Code

[Smaug123]

Fixed in 57a533c. The anonymous-name counter now starts past any sanitised definition/response name of the form Type{N}, so the spec's own Type1 is preserved and the inline schema becomes Type2.

Verified at the level this repo tests generators: swagger-anonymous-types.json in ConsumePlugin defines Type1 alongside an inline object response, so a regression fails the build with FS0037 (observed before the fix). An in-process generate test isn't currently possible: WoofWare.Expect forces Fantomas.FCS 7.0.3 in the test project, which is binary-incompatible with the Fantomas.FCS 6.1.1 that WoofWare.Whippet.Fantomas 0.7.3 was compiled against, so calling the generator's AST construction from the test host throws MissingMethodException.

The fix has been merged forward through the rest of the stack (#543–#546); each branch rebuilt and passed its full suite.

[Smaug123]

Fixed in a196b18. Confirmed the overflow: a definition named Type2147483647 seeded the counter to Int32.MaxValue, the next increment wrapped, and the generated file declared Type2147483648 (sanitised) while referencing Type-2147483648 — FS0010, as you predicted.

As suggested, the seeding scheme is gone: defnToType now takes a nextAnonymousTypeName : unit -> string allocator, built in generate over a set of taken (sanitised) definition/response names, which skips occupied Type{N} names one at a time. No spec-supplied name can move the counter, so wraparound would require actually generating 2^31 anonymous types.

swagger-anonymous-types.json now also defines Type2147483647 (structurally distinct from Type1, since identical shapes are deduplicated into one generated type), so both the collision and the overflow break the build if reintroduced. Propagated through #543–#546; all branches green.