docs: enable versioning feature

[heitorlessa]

Issue #, if available:

Description of changes:

This will address a common challenge of having staged changes not being visible in the documentation, or the need for banners like New in X due to not having docs related to a particular release.

• Include mike in mkdocs.yml
• Configure versions and alias
• Automate versioned deploys for develop and upon new releases
• Version API ref docs per develop as well as releases e.g., /develop/api, /1.15.0/api
• Create redirect from old links to latest alias

Demo: https://heitorlessa.github.io/powertools-docs-versioning/latest/

This will introduce a /<version> in the URL and will break bookmark links, since GH Pages doesn't support redirects. Redirecting might work with mkdocs-redirects plugin, though we might reactively fix it as I'm not sure whether pages have been bookmarked as >90% of customers come straight to index then navigate.

Update: Thanks to @saragerion, including a 404.html in the root of GH Pages works to preserve old docs to latest version.

Checklist

• Meet tenets criteria
• Update tests
• Update docs
• PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

• Migration process documented
• Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.