[Docs] Implement small docs changes about compatibility, plotly express and versioning

[maxschulz-COL]

Description

Addresses https://github.com/McK-Internal/vizro-internal/issues/444

• [x] add to docs that not refer to front-end changes as breaking changes
• [x] add to docs about browser support (that support Chrome, and other browsers may work but are not officially supported)
• [x] Make more apparent when px charts need capture or not, see context: https://quantumblack.slack.com/archives/C02HQNRQYF2/p1707404245314859

Screenshot

Notice

• [x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

  • I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
  • I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
  • I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
  • I have not referenced individuals, products or companies in any commits, directly or indirectly.
  • I have not added data or restricted code in any commits, directly or indirectly.

[maxschulz-COL]

Great! Do we want to keep the new Compatibility page under the Explanation or move it to the Contribute section?

So I felt it was better placed here, as this is independent of contributing, but rather a general explanation about our product. Curious to see what @stichbury thinks

[stichbury]

I like it! I think you're right to keep the compatibility separate from the contribution content. I also think the explanation section is probably the best right now. I'm leaning towards creating an FAQ page in the Get Started section where this content would probably fit best, and other FAQs would come out of the explanation page (ideally we will scrap that page entirely in due course and relocate the content). The contributor FAQs should stay where they are in that section.

Let's leave where you've placed it for now but we can be mindful that it may move. Sound reasonable? @maxschulz-COL @antonymilne @huong-li-nguyen ?