Update CI and docs for Python up to py311

[IAlibay]

Summary of changes

• Update CI to add py310 and py311
• Added cron entry for CI
• Added classifiers for new python versions
• Removed universal wheels (propka doesn't support py2.x anymore)

[codecov[bot]]

Codecov Report

Base: 73.09% // Head: 73.05% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (3e897b7) compared to base (8acfb4f). Patch has no changes to coverable lines.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #150 +/- ## ========================================== - Coverage 73.09% 73.05% -0.04% ========================================== Files 25 24 -1 Lines 3970 3968 -2 ========================================== - Hits 2902 2899 -3 - Misses 1068 1069 +1 ``` | [Impacted Files](https://codecov.io/gh/jensengroup/propka/pull/150?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=jensengroup) | Coverage Δ | | |---|---|---| | [propka/protonate.py](https://codecov.io/gh/jensengroup/propka/pull/150/diff?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=jensengroup#diff-cHJvcGthL3Byb3RvbmF0ZS5weQ==) | `88.26% <0.00%> (-0.40%)` | :arrow_down: | | [propka/\_\_init\_\_.py](https://codecov.io/gh/jensengroup/propka/pull/150/diff?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=jensengroup#diff-cHJvcGthL19faW5pdF9fLnB5) | | | Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=jensengroup). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=jensengroup)

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[speleo3]

What's the rational for triggering two builds a week?

[IAlibay]

What's the rational for triggering two builds a week?

We've been doing twice a week in other places (MDAnalysis, etc...) since we have lots of dependencies that update randomly, but I agree that it's probably too much for this repo.

Once a week or more infrequently? I suspect the cron job is going to get disabled once in a while anyways if the commit frequency is too low (> 6 weeks).

[speleo3]

Thanks for clarifying. Once a week sounds good to me, we can always change it if needed.

[sobolevnrm]

Thank you for the PR, @IAlibay !