…calls (#9726)

<!--

Please, go through these steps when you submit a PR.

1. Make sure your branch is not protected. In particular, avoid making
PRs from the `main` branch of your fork.

2. Give a descriptive title to your PR. We use semantic titles, and the
accepted types and scopes are listed in
https://github.com/meltano/meltano/blob/main/.github/semantic.yml.

   A good title should look like this:

   ```
feat(cli): The `meltano run` command now accepts a `--timeout` option to
limit the time it runs
   ```

3. Provide a description of your changes.

4. Put "Closes #XXXX" in your comment to auto-close the issue that your
PR fixes (if such).

-->

## Description

<!-- Describe the changes introduced by this PR -->

## Related Issues

* python-jsonschema/check-jsonschema#635

## Summary by Sourcery

Replace external check-jsonschema CLI usage with direct jsonschema-based
manifest validation and extend tests to cover schema validation behavior
and logging.

Bug Fixes:
- Ensure manifest schema validation logs include nested JSON path
information for deeply nested schema violations.

Enhancements:
- Refactor manifest schema validation to use jsonschema.Draft7Validator
directly instead of invoking the check-jsonschema subprocess.
- Remove the unused check-jsonschema dependency from the project
dependencies.

Build:
- Drop check-jsonschema from runtime dependencies in pyproject.toml.

Tests:
- Add tests verifying that valid manifests lint cleanly without schema
warnings and that nested schema violations produce appropriate warning
logs with nested paths.

## Summary by Sourcery

Replace external manifest schema validation via the check-jsonschema CLI
with direct jsonschema-based validation and improve how schema
validation results are logged and tested.

Bug Fixes:
- Ensure schema validation warnings include precise JSON paths for
root-level and nested manifest schema violations.

Enhancements:
- Introduce a cached jsonschema-based validator for the manifest schema
instead of invoking the check-jsonschema subprocess.
- Simplify manifest environment location discovery to use the loaded
manifest schema data.
- Improve schema validation warning formatting to aggregate and present
all errors in a structured, readable message.

Build:
- Remove the check-jsonschema dependency from the project runtime
dependencies.

Tests:
- Add tests to assert that valid manifests lint without schema warnings
and that invalid manifests, including nested violations, produce
appropriate warning logs with full JSON paths.

---------

Signed-off-by: Edgar Ramírez Mondragón <[email protected]>