Feat: Add --path Option to Target Specific Schema Parts in validate Command

[Karan-Palan]

What kind of change does this PR introduce?

• Feature: Added support for the --path (or -p) option in the validate command to allow targeting specific parts of a JSON schema using JSON Pointers.

Issue Number:

• Closes Add a --path option to commands like validate #218

Screenshots/videos:

Screencast.from.2025-02-02.12-53-07.webm

If relevant, did you update the documentation?

Not yet

Summary

This PR introduces the --path (-p) option to the validate command, enabling users to specify a JSON Pointer for validating a sub-schema within a larger JSON schema. This is especially useful for OpenAPI specs and complex JSON structures where validation may be needed for specific nested sections.

Key changes:

• Added --path/-p option to CLI parser.
• Integrated JSON Pointer resolution to extract the specified sub-schema.
• Added error handling for invalid pointers or sub-schemas.

Does this PR introduce a breaking change?

• No breaking changes. The new option is fully backward-compatible. Existing workflows without the --path option will continue to function as expected.

[jviotti]

Awesome! Great first step. Can you fix the formatting issues and add a couple of test cases (at least one where the pointer exists and one where it doesn't)?

[Karan-Palan]

Awesome! Great first step. Can you fix the formatting issues and add a couple of test cases (at least one where the pointer exists and one where it doesn't)?

Thanks!
I fixed the linting errors - they were because my clang default was set to chromium's source. I also added some tests and docs (it's my first time writing tests in shell :p)
Please review when you get the time!