Relax Python version requirement from >=3.13 to >=3.10

[MaxGhenis]

Problem

pyproject.toml currently requires >=3.13,<3.14, but this appears to be unintentional:

1. The old setup.py had python_requires=">=3.7"
2. policyengine-us uses >=3.10,<3.14
3. policyengine-core uses >=3.10
4. The classifiers in pyproject.toml list Python 3.10, 3.11, 3.12, 3.13

When pyproject.toml was introduced in PR #1395 (Nov 2025), it was set to >=3.13 rather than matching the previous >=3.7 or aligning with other PE packages.

Impact

Users on Python 3.10-3.12 get a confusing pip error:

ERROR: Could not find a version that satisfies the requirement policyengine-uk==2.72.3

This particularly affects Modal deployments and other environments that default to Python 3.11.

Proposed Fix

Change in pyproject.toml:

requires-python = ">=3.10,<3.14"

This aligns with policyengine-us and should work unless there's a specific 3.13+ dependency I'm not aware of.

[MaxGhenis]

Closing as addressed. Current main no longer requires >=3.13; pyproject.toml now declares requires-python = ">=3.11". So the original packaging bug described here is fixed. The remaining question is whether 3.10 support is worth pursuing later, but that is now a separate dependency decision rather than the old accidental 3.13 floor.

[MaxGhenis]

Current main is no longer >=3.13; it now requires >=3.11. So the original floor-regression part of this issue is resolved. The remaining open question is specifically whether we want to support 3.10, and the current blocker there is tables>=3.10.2, which requires Python 3.11+.

[MaxGhenis]

Current main is no longer on the old >=3.13,<3.14 floor. It is now requires-python = ">=3.11". The remaining gap versus this issue is specifically Python 3.10 support, and the concrete blocker appears to be tables>=3.10.2, which currently requires 3.11+. So this issue is now narrower than originally reported.