chore: Update supported Python versions through copier template update

[DiamondJoseph]

Adds support for Python 3.13 and drops for Python <=3.10 following the Numpy deprecation policy, and keeps dependencies, CI and infrastructure up to date with Diamond standards.

Instructions to reviewer on how to test:

1. Ensure that CI passes on all versions to remain supported

Checks for reviewer

• Would the PR title make sense to a user on a set of release notes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.34%. Comparing base (b04469b) to head (dab7661).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #59   +/-   ##
=======================================
  Coverage   99.33%   99.34%           
=======================================
  Files           4        4           
  Lines         453      455    +2     
=======================================
+ Hits          450      452    +2     
  Misses          3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Araneidae]

I would recommend rejecting this PR merely based on the title and description. Please fix this and the corresponding commit description.

Updating the python requirement should definitely be a commit of its own.

[AlexanderWells-diamond]

This repo also maintains a changelog.rst. I understand the copier template does away with at least some of the requirements of maintaining it, but at least a note in there to say the file should no longer be updated should be added.

[DiamondJoseph]

@AlexanderWells-diamond I've added a changelog entry- it looks like the change of supporting 3.13 will need to be continued upstream to epicscorelibs. This has come from wanting to support Python 3.13 in blueapi/dodal/ophyd-async in keeping with the NumPy deprecation policy.

@Araneidae the Python version support is defined in a section of the pyproject.toml that is modified by the python copier template in this update. To keep the tooling compatible and up to date, to allow future automating of updates and to prevent merge conflicts with all future updates to either, I'd like to keep them both together. Propagating those changes from the template means the whole organisation can move forward faster.

[DiamondJoseph]

I've left this as a draft as epicscorelibs support is still required