Add Python 3.14 to the compatibility matrix

We currently cap Python support below 3.14 and don't test against it. `pyproject.toml` line 8 has `requires-python = ">=3.10,<4,<3.14"`, and the CI matrix in `.github/workflows/main.yaml` line 40 is `[ "3.10", "3.11", "3.12", "3.13" ]`. We should add 3.14 to the test matrix and drop (or bump) the `<3.14` cap.

The real question is dependency support, not the version bump. The `<3.14` cap and the earlier `<3.13` cap from #857 both existed because a transitive dependency (semsimian) forced them. Before relaxing the cap we need to confirm that _semsimian_ ships 3.14 wheels, and check the other dependencies that have already caused friction: eutils (pinned via #852), and curies/pronto (recent commits `296d3b543` and `f70006072` guard against a pronto backtrack and removed a curies upper pin).

If any of those don't support 3.14 yet, that dependency is the blocker and this stays open until it's resolved upstream.

And, of course https://github.com/ontology-tools/py-horned-owl/issues/58 which is implemented but not released yet.

## Related

- #857 — precedent: semsimian forced a down-version below 3.13, the same dependency likely gates 3.14
- #852 — eutils pin, one of the dependencies to re-check against 3.14
- https://github.com/ontology-tools/py-horned-owl/issues/58

Start with the Python requirement in pyproject.toml line 8 and the version matrix in .github/workflows/main.yaml line 40. Check whether semsimian provides Python 3.14 wheels, then re-check eutils and the curies/pronto changes, along with the unreleased py-horned-owl issue #58. Done means the dependencies support 3.14 and the updated cap and CI matrix pass.

Written by the indexing model from the issue text.