Update tested python versions

[rstoneback]

Description

Addresses #(issue)

Updates Python versions tested as well as address security update in readthedocs

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Online testing

Checklist:

• [x] Make sure you are merging into the develop (not master) branch
• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] Add a note to CHANGELOG.md, summarizing the changes

[rstoneback]

Hey @jklenzing do you have any ideas on why coveralls is rejecting some of the coverage info, but not others? It somehow got worse when I went from testing 4 python versions down to 3 :(

Searching on the web the fixes are to include things like run: coveralls --rcfile=setup.cfg --service=github which is already in main.yml for workflows.....

[rstoneback]

Previous test run https://github.com/rstoneback/OMMBV/actions/runs/7618467786

[rstoneback]

Thanks @jklenzing , the info in pysat saved the day once again 👍