Minimal response-model extracts from provider OpenAPI specs. Each file defines
the required fields for one API endpoint response, used by
`tests/schema_validation.rs` to verify our golden fixtures stay in sync with
upstream specs.
- ------
Paths use the same syntax as `assert_has_key`: dots for nesting, `[0]` for
array indexing (checks first element).
When a provider updates their API spec:
1. 2.3.4.
AWS (XML, no OpenAPI), Proxmox (no published spec), i3D.net (no published spec)
and TransIP (no published spec) are validated by contract snapshot tests only.