Group mkdocs version bumps

[twz123]

Description

There might be cases in which some mkdocs extensions pin certain minor mkdocs versions. Then we're forced to update them in lockstep with the main mkdocs version.

See:

• Bump mkdocs from 1.5.3 to 1.6.0 in /docs #4326
• Bump mkdocs-material from 9.5.18 to 9.5.20 in /docs #4352

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• 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
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings