Drop numpy upper bound, run CI weekly

[wrignj08]

Drop the numpy upper bound

numpy>=2.0,<2.4 → numpy>=2.0.

The cap existed to keep numba installable, but numba is not a runtime dependency — it only enters through the dev group, via s2mosaic → numbagg → numba. The bound therefore constrained every downstream install to protect a package users never receive. numba also declares its own ceiling (numpy<2.6 as of 0.67), so the resolver handles the dev-side constraint without help.

A fresh resolve after the change:

	before	after
numpy (3.12+)	2.3.5	2.5.2
numpy (3.11)	2.3.5	2.4.6
numpy (3.10)	2.2.6	2.2.6
numba	0.64.0	0.67.0
llvmlite	0.46.0	0.49.0

3.11 stops at 2.4.6 and 3.10 at 2.2.6 because numpy dropped those interpreters, not because of anything in our tree.

Full non-e2e suite passes on the upgraded set — 163 passed, 36 deselected, on 3.13 / numpy 2.5.2.

Run CI weekly

Adds schedule: "0 0 * * 0" (Sundays 00:00 UTC) and workflow_dispatch.

uv.lock is gitignored, so uv resolves fresh on every CI run — a scheduled build tests against current upstream releases and will surface a breaking numpy or numba version before users hit it. That matters more now that the upper bound is gone.

e2e tests stay excluded; they need a GPU, which GitHub-hosted runners don't provide.

Notes

• No CHANGELOG entry yet — to be added after merge.
• GitHub disables cron on repos with no commits for 60 days, so a silent absence of runs is worth knowing about as a failure mode.

🤖 Generated with Claude Code