Update python versions - 3.7 deprecation, 3.10 and 3.11 testing support

[gwaybio]

Description

With python 3.7 security end of life in 2 weeks, this update is required prior to version 1 release. This also addresses #259.

What is the nature of your change?

• Bug fix (fixes an issue).
• Enhancement (adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• This change requires a documentation update.

Checklist

Please ensure that all boxes are checked before indicating that a pull request is ready for review.

• I have read the CONTRIBUTING.md guidelines.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have deleted all non-relevant text in this pull request template.

[codecov-commenter]

Codecov Report

Merging #287 (6168197) into master (77d93a3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #287   +/-   ##
=======================================
  Coverage   95.12%   95.12%           
=======================================
  Files          57       57           
  Lines        3057     3057           
=======================================
  Hits         2908     2908           
  Misses        149      149           

Flag	Coverage Δ
unittests	95.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
setup.py	0.00% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[d33bs]

Nice changes! Generally I thought your changes looked good. I did have questions regarding the additional files / thoughts below and wanted to get your input. Thanks in advance!

• Would it make sense to update the Python version in .readthedocs.yml?
• I think we might be able to bump the version of pre-commit in requirements-dev.yml to v3.x.x as per comments in Drop support for Python 3.7; Potentially add support for Python 3.10 & Python 3.11 #273 (there are also other steps @kenibrewer mentions which may need attention regarding the devcontainer files).
• Should we set a reminder or create a new issue for Python 3.8 EoL (October 2024 sometime)?

[gwaybio]

Would it make sense to update the Python version in .readthedocs.yml?

Yep, I will add

I think we might be able to bump the version of pre-commit in requirements-dev.yml to v3.x.x as per comments in
#273 (there are also other steps @kenibrewer mentions which may need attention regarding the devcontainer files).

Thanks for pointing to this issue! I missed this. Will review and make corresponding changes here.

Should we set a reminder or create a new issue for Python 3.8 EoL (October 2024 sometime)?

I think this is optional.

[gwaybio]

Thanks for the review @d33bs ! This is ready for another round

[d33bs]

Thanks for addressing the comments @gwaybio - LGTM!