Add configurable input options to Python tox unit testing workflow

[zachcran]

Description

Right now, the workflow for Python unit testing via tox is hard-coded to use Python versions 3.9 and 3.11. Python 3.9 is reaching EOL soon and Python 3.12 and 3.13 have both been released as higher stable versions. Our reusable workflow needs to be more flexible to allow different projects to use it to test against different Python versions. Since it is the same pattern, I also made the test platforms configurable through an input value.

This is going to change the behavior of the workflow in any repos that currently refer to this workflow, so I have compiled a list of our repos that need to be updated. However, none of them are public at the moment, so please reach out if you need the list of repos to be converted.

TODOs

• Double-check that this implementation works. It is hard to do this without creating an entire separate test organization, so I vote that we just merge it and fix issues as we see them.

[github-actions]

🏷️ [bumpr]
Next version:v0.1.0
Changes:v0.0.1...RxnRover:add_configurable_inputs_to_tox_testing

[zachcran]

@dulithaprasanna @sunerawijeratne Since you have repos that may use this reusable workflow, I wanted to request review from you as well to make sure you are okay with the changes and notify you that this is likely coming down the pipeline. Your current workflows will still work, but they won't test on all of the versions of Python or OSes that they did before by default.

Perhaps it would be best to add an example workflow file that can be easily copy-pasted to other projects to make the change easier. I'll try that and see if it causes issues to add it here.

[github-actions]

🚀 [bumpr] Bumped!
New version:v0.1.0
Changes:v0.0.2...v0.1.0