- Changed parseExtensions to use Record<string, unknown> instead of any
- Added type assertions at call sites for type safety
- Restored SpecificationExtensions to CallbackObject, PathsObject, ResponsesObject
- Kept PathsObject with [path: /${string}] template literal type
- Extended index signatures with | unknown to satisfy TypeScript

Co-authored-by: mrlubos <12529395+mrlubos@users.noreply.github.com>

- Changed parseExtensions to use any types instead of generic constraints
- Removed SpecificationExtensions from interfaces with index signatures (CallbackObject, PathsObject, ResponsesObject)
- Changed PathsObject index signature from /${string} to string for compatibility
- These changes fix TypeScript errors while preserving extension field support

Co-authored-by: mrlubos <12529395+mrlubos@users.noreply.github.com>

Co-authored-by: mrlubos <12529395+mrlubos@users.noreply.github.com>

- Created SpecificationExtensions interface in 3.0.x and 3.1.x spec.d.ts
- Applied to all 27 interfaces that support extensions in each version
- Replaced inline `[extension: x-${string}]: unknown` with extends clause
- Also added SpecificationExtensions to JsonSchemaDraft2020_12

Co-authored-by: mrlubos <12529395+mrlubos@users.noreply.github.com>

- Made parseExtensions generic and exportable from schema parsers
- Reused parseExtensions in parameter and operation parsers
- Removed JSDoc comments from extension field index signatures

Co-authored-by: mrlubos <12529395+mrlubos@users.noreply.github.com>

Co-authored-by: mrlubos <12529395+mrlubos@users.noreply.github.com>

Co-authored-by: mrlubos <12529395+mrlubos@users.noreply.github.com>

Fix: Support moduleResolution "node16" alongside "nodenext"

docs: normalize changesets