Static versioning in pyproject.toml is conflicting with version.py versioning

`version.py` and the dynamic version in `pyproject.toml` were intended to work in tandem, with further checks on forced version updates with every PR. It's hardcoded in `pyproject.toml` and is not checked in CI.

That was a HACK due to the issues of scikit-build. Thus, to resolve the issue, it is recommended to verify the compatibility of scikit-build and `pyproject.toml`, or consider using the hatchling library as an alternative for wheel building.

Start by comparing the static version in pyproject.toml with the dynamic version.py setup and reviewing the scikit-build compatibility concerns described in the issue. Investigate whether the current build configuration or hatchling can provide consistent versioning, then verify that forced version updates are checked in CI; done means the two versioning approaches no longer conflict and CI enforces the intended check.

Written by the indexing model from the issue text.