[codex] Add OpenAPI 3.2 support

[closedLoop]

Summary

• accept openapi: 3.2.0 in the parser version gate
• extend the bundled OpenAPI 3.1 schema at runtime with a targeted 3.2 compatibility layer for key additions such as query, additionalOperations, itemSchema, mediaTypes, response summary, richer tag metadata, querystring parameters, and OAuth 2.0 metadata/device authorization fields
• add parse and schema-validation coverage for OpenAPI 3.2 documents

Why

swagger-parser currently rejects OpenAPI 3.2.0 before validation even starts. In addition, @apidevtools/openapi-schemas has not yet published a native v3.2 schema, so this change layers the main 3.2 additions onto the existing 3.1 schema in-process so consumers can start validating representative 3.2 documents now.

Validation

• npx mocha test/specs/invalid/invalid.spec.js test/specs/validate-schema/validate-schema.spec.js
• npx eslint lib test
• npm test