[docs] Direct users from Material UI to MUI Base for duplicated components

[mapache-salvaje]

Closes #35077 (at least until these components are removed from Material UI in the future)

This PR addresses the issue of outdated pages in the Material UI docs that cover components that are exact duplicates from MUI Base:

• Click-Away Listener
• No-SSR
• Portal
• Textarea Autosize

I have deleted the content from the Material UI pages, and replaced it with an info callout directing users to the MUI Base docs:

https://deploy-preview-35293--material-ui.netlify.app/material-ui/react-click-away-listener/

[mui-bot]

	Messages
📖	Netlify deploy preview: https://deploy-preview-35293--material-ui.netlify.app/

No bundle size changes

Generated by 🚫 dangerJS against bff31fc

[oliviertassinari]

@samuelsycamore As a continuation of #35293 (comment), when I land on https://deploy-preview-35293--material-ui.netlify.app/material-ui/react-click-away-listener/ as a developer, I might struggle a bit to:

1. Find the new docs. I didn't really read the content. I skipped read. I intuitively clicked on the first link thinking it would be MUI Base ClickAwayListener page. Should we have the first link to point to the most relevant page?
2. Find what's the stable import path. We do no longer document explicitly, to consider if it's fine.

[mapache-salvaje]

Those are both good points @oliviertassinari. I can rearrange the text a bit so that the first link goes to the component page. As for 2, should we provide the Material UI import or the MUI Base import on this page? It does make sense to give the Material UI import here since we're saying it's re-exported for convenience, but then again it feels a bit odd to give this import while at the same time informing users that it's going to be deprecated. I guess the Material UI import is preferable for now, until MUI Base gets a stable release.