…ith Hatch/uv for improved PEP 735 compliance.

This involves modernizing the project's configuration, focusing on PEP 735 compliance, Hatch environment cleanup, dependency consolidation, and ensuring consistency across various configuration files.

Here's a summary of the key changes:

**1. `pyproject.toml` Enhancements:**
    - I standardized the Hatch environments to use `uv` as the installer.
    - I removed redundant dependencies from `[dependency-groups.dev]` and `[dependency-groups.docs]`.
    - I simplified the `[tool.hatch.envs.test-optional]` environment by removing inherited dependencies.
    - I migrated logic from `scripts/pycheck.sh` and `scripts/test-lsp.sh` into new Hatch environments (`lint` and `test-lsp`) and scripts within `pyproject.toml`.

**2. `Makefile` Adjustments:**
    - I updated the `py-check` target to use the new consolidated Hatch script (`hatch run default:pycheck`).

**3. `scripts/` Directory Cleanup:**
    - I removed `scripts/buildwheel.sh` (as it's redundant with `hatch build`).
    - I removed `scripts/pycheck.sh` (since its functionality was moved to `pyproject.toml`).
    - I removed `scripts/test-lsp.sh` (as its functionality was also moved to `pyproject.toml`).

**4. `.github/workflows/dev_build.yaml` Streamlining:**
    - I changed `pixi run make py` to `pixi run hatch env create default` to align your CI with Hatch environment management.

These changes should contribute to:
    - Centralized task definition within Hatch.
    - Consistent and faster dependency management with `uv`.
    - Reduced redundancy in your configurations.
    - Better alignment of CI processes with the Hatch workflow.
    - Improved overall maintainability and a more streamlined development process for you.