[docs] Fix versions page

[mnajdova]

I am thinking of duplicating the vresions pages on Core and X docs, first of all because historically they had different release pace. I've extracted the logic for generating the versions in one place so we can reuse it. Some of the content will be duplicated, but I still think it's fine to have two different pages. The current page can't be in the current shape directly reusable on MUI X anyways.

Todo:

• make sure the next.mui.com is down before moving forward
• cherry pick the change in older docs
• Add back all versions in the select on older versions's docs
• Do the same PR on MUI X

[mui-bot]

Netlify deploy preview

• docs/data/material/components/about-the-lab/about-the-lab.md
• docs/data/material/getting-started/support/support.md
• docs/data/material/getting-started/supported-platforms/supported-platforms.md
• docs/data/material/getting-started/versions/versions.md
• docs/data/material/migration/migration-v3/migration-v3.md

Bundle size report

Bundle	Parsed size	Gzip size
@mui/material	0B(0.00%)	0B(0.00%)
@mui/lab	0B(0.00%)	0B(0.00%)
@mui/system	0B(0.00%)	0B(0.00%)
@mui/utils	0B(0.00%)	0B(0.00%)

Details of bundle changes

Generated by 🚫 dangerJS against c524629

[mnajdova]

Potentially revert this if it is a local issue

[Janpot]

Maybe it makes sense to build this like the notifications? a json on master with all the versions, then fetch it in getStaticProps. Then we don't need to update every old branch when a new version comes out, just deploy it.

[mnajdova]

Maybe it makes sense to build this like the notifications? a json on master with all the versions, then fetch it in getStaticProps. Then we don't need to update every old branch when a new version comes out, just deploy it.

With this logic too we don't need to update older versions (once they get to this version). The difference would be that this logic depends on the docs branches, and that one would be manually created. I am ok with that option too, it's simple.