feat(schema): add support for JSON Schema $defs and definitions

[arcaputo3]

Added support for $defs and definitions properties in JsonSchema record to handle JSON Schema references properly. Added tests to verify both formats work correctly.

🤖 Generated with Claude Code

Motivation and Context

This change addresses issue #145 by adding support for both $defs and definitions properties in the JsonSchema record. Previously, the schema couldn't properly handle JSON Schema references that use these properties,
which are essential for defining complex schema structures with reusable components.

How Has This Been Tested?

Added comprehensive unit tests that verify:

• Parsing JSON Schema with $defs property
• Parsing JSON Schema with definitions property
• Serializing and deserializing schemas with references
• Working with tools that use complex schemas containing references

Breaking Changes

None. This is a backward-compatible enhancement to the existing JsonSchema implementation.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

This implementation supports both the older definitions keyword and the newer $defs keyword (introduced in JSON Schema draft 2019-09) to ensure compatibility with different JSON Schema versions.

[chemicL]

Thanks for the contribution!

[CodeSpaceiiii]

@chemicL When will this merge release a new version? This specific is very important to us, thank you.

[chemicL]

@CodeSpaceiiii the 0.10.0 milestone is currently scheduled for May 12.
I would love to learn what scenarios this feature enables for you, would you be interested in providing some basic samples or contributing a documentation improvement?

[arcaputo3]

@chemicL FWIW the reason for the PR personally was for using Tapir schemas in my FastMCP-Scala project. Tapir serializes case classes as definitions and uses references in the properties. You can get around this by simply flattening the definitions into the properties, but this might be inefficient especially if your schema references the same definition more than once.