fix(aide): apply schemars transforms to inlined schemas

[abbudao]

Supersedes #230, part of #270.

As @Diggsey made the original report and analysis, I made him co-author on the commit.

Intent

aide never applies its schemars settings to the schemas it inlines.

schemars runs the transforms from SchemaSettings in two places, root_schema_for and take_definitions(true), and aide uses neither when building an operation. It calls subschema_for::<T>() and reads the result back through GenContext::resolve_schema, which is a plain lookup. Nothing on that path transforms anything. (Diggsey's description on #230.)

You don't need custom settings to hit this. aide's own generator is built from SchemaSettings::draft07(), which already ships ReplacePrefixItems and friends, so a Query<T> over

struct Params { range: (u8, u8) }

emits prefixItems into a document that announces draft 7. Validators ignore keywords they don't know, so that parameter accepts any array at all. Definitions under #/components/schemas were always fine since merge_api_with collects them with take_definitions(true); only the inlined half was wrong.

Proposed Changes

GenContext gets resolve_schema_transformed (resolve a ref, return a transformed copy) and apply_transforms (transform in place). Every site that embeds a generated schema now uses one: parameters_from_schema, the media types for Json and both Forms, and TypedHeader.

apply_transforms skips $refs on purpose. They have to stay references, and their targets get transformed at merge time. That's also what makes one path work under both extract_schemas modes.

TypedPath had the reverse problem. It reads its description from root_schema_for, which does transform, then reused that schema for the parameters, so they'd now be transformed twice. Transform promises nothing about idempotency, so it takes parameters from subschema_for like every other caller.

Two differences from #230. Its parameters_from_schema change is here as-is. Its axum/inputs.rs change isn't: at that site the resolved schema is only read for .get("description") while the MediaType gets the untouched json_schema, so the transformed clone was discarded two lines later. I transformed the schema that actually gets embedded instead. That same shape turned up in five more places #230 missed (both Form inputs, both operation_response impls, TypedHeader), all fixed here.

Breaking Changes

None to the API, both methods are additive. Tested on both schemars 1.0.4 and 1.2.2.

[MOZGIII]

I've glanced though this, and although I have nothing to do with this PR or project - the patch looks good to me

[jplatte]

I'll try to get to this soon!