Remove Python 3.8 and add Python 3.13

[mavaylon1]

Remove Python 3.8 and add Python 3.13
Fix #234

Checklist

• Did you update CHANGELOG.md with your changes?
• Have you checked our Contributing document?
• Have you ensured the PR clearly describes the problem and the solution?
• Is your contribution compliant with our coding style? This can be checked running ruff from the source directory.
• Have you checked to ensure that there aren't other open Pull Requests for the same change?
• Have you included the relevant issue number using "Fix #XXX" notation where XXX is the issue number? By including "Fix #XXX" you allow GitHub to close issue #XXX when the PR is merged.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.73%. Comparing base (6fd9d53) to head (d1face9).

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #240      +/-   ##
==========================================
+ Coverage   86.65%   86.73%   +0.08%     
==========================================
  Files           5        5              
  Lines        1206     1206              
  Branches      304      229      -75     
==========================================
+ Hits         1045     1046       +1     
  Misses        102      102              
+ Partials       59       58       -1     

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[rly]

Parallel write tests are failing on Windows with Python 3.13. Not sure why. I also ran all tests on this branch to see if it is only Python 3.13: https://github.com/hdmf-dev/hdmf-zarr/actions/runs/11968032434

If it is only Python 3.13 and there is no easy fix, I propose, in the interest of our schedules, that we remove python 3.13 support (just remove the line from pyproject.toml) for now, and we can add it in a later version of hdmf-zarr. We can keep the tests and CI as they are while we work through the issue.

[mavaylon1]

@rly If I understand what you are saying, keep the testing with 3.13 but remove support for 3.13 for users via pyproject.toml. To do that I think we have add a <3.13, not just comment out the classifier part. I believe that is just metadata.

[rly]

The Windows Python 3.13 error was fixed in pytest 8.1.0: pytest-dev/pytest#11875

I think updating pytest and related dependencies should resolve the error (I just pushed changes for that to this branch). We should update all the fixed testing dependencies before the 1.0 release anyway.