feat: Separate SchemanticType to a new package

[natebosch]

Closes #222

The schemantic package has a heavy set of dependencies including
analyzer which makes it a poor candidate to be a shared dependency
across all implementations of JSON schema libaries that users may want
to use with package:genkti. Pull out SchemanticType to a new package
with fewer dependencies that may allow for other JSON schema libraries
to take a dependency and implement SchemanticType for compatibility.

Move validate to an extension method so that the implementation and
error interfaces can remain in package:schemantic.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the schemantic package by extracting the fundamental SchemanticType interface into a new, dedicated package called schemantic_api. This strategic separation aims to reduce the dependency burden on the core type definition, thereby enhancing its reusability and enabling greater compatibility for package:genkti with diverse JSON schema implementations. The validate method was also adapted into an extension to maintain functionality within the original schemantic package.

Highlights

• New schemantic_api package created: A new package, schemantic_api, was introduced to house the core SchemanticType interface and its related metadata, significantly reducing its dependencies.
• Relocation of SchemanticType: The SchemanticType class, along with JsonSchemaMetadata and static schema creation methods, was moved from package:schemantic to the new package:schemantic_api.
• Validation method refactored: The validate method, previously part of the SchemanticType abstract class, was converted into an extension method on SchemanticType within package:schemantic. This change allows the validation logic to remain in schemantic while the core interface is in schemantic_api.
• Dependency reduction for core interface: By separating SchemanticType, the core interface now has a much lighter dependency footprint, making it more suitable for broader adoption and compatibility with other JSON schema libraries in package:genkti.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the schemantic package by extracting the core SchemanticType abstract class, its associated metadata, static schema factory methods, and internal schema building logic into a new schemantic_api package. The schemantic package now depends on and re-exports SchemanticType from schemantic_api, and the validate method has been moved to an extension on SchemanticType within schemantic. This modularization separates the API definition from its primary implementation, with a note in the changelog about potential static diagnostics for classes that previously overrode the validate method.