docs: correct old python versions in docs page

[AleJo2995]

Types of changes

• [ ] Hot fix (emergency fix and release)
• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Documentation (change which affects the documentation site)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Release (develop -> main)

Quality assurance (all should be covered).

• [x] My code follows the code style of this project.
• [x] Documentation for my change is up to date?
• [x] My PR meets testing requirements.
• [x] All new and existing tests passed.
• [x] All commits are signed-off.

Summary

Closes #1570

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[AleJo2995]

@degenaro this PR should be enough to correct python versions on the webpage as discussed. If there's any other part they need to be corrected let me know so I can correct and commit the changes if needed

[AleJo2995]

@degenaro , @vikas-agarwal76 could you please review and approve this? Thanks