[docs] Improve the Base documentation

[michaldudak]

Make the Base docs comprehensive and compliant with our Style Guide (https://www.notion.so/mui-org/Style-guide-2a957a4168a54d47b14bae026d06a24b).

This is a follow-up to #31414.

Docs to review

• Getting started

  • Installation - [docs] Base Installation style revisions and final review #32483
  • Overview - [docs] Add "Overview" page to Base docs #32310
  • Usage & Customization - [docs] Move, split, and revise "Unstyled components" page #32562

• Components

  • Input - [docs] Base Input style revisions and final review #32096
  • Select - [docs] Base Select style revisions and final review #32095
  • Slider - [docs] Base Slider style revisions and final review #32140
  • Menu - [docs] Base Menu style revisions and final review #32097
  • Badge - [docs] Base Badge style revisions and final review #32098
  • Modal - [docs] Base Modal style revisions and final review #32093
  • Form control - [docs] Base Form Control style revisions and final review #32309
  • Table pagination - [docs] Base TablePagination style revisions and final review #32178
  • Trap focus - [docs] Base TrapFocus style revisions and final review #32364
  • Popper - [docs] Base Popper style revisions and final review #32412
  • Tabs - [docs] Base Tabs style revisions and final review #32423
  • No SSR - [docs] Base NoSsr style revisions and final review #32254
  • Click-away listener - [docs] Base ClickAwayListener style revisions and final review #32156
  • Button - [docs] Base Button style revisions and final review #32380
  • Textarea autosize [docs] Base TextareaAutosize style revisions and final review #32481
  • Portal - [docs] Base Portal style revisions and final review #32157
  • Switch - [docs] Base Switch style revisions and final review #32376

[samuelsycamore]

After reviewing #32364, I'm starting to notice formatting inconsistencies across these docs that I didn't catch when reviewing individually—for example, some include import code snippets and lists of Features, and others do not.

Once the individual revisions are done, I'll go back for one final pass to clean up all the little details across the board on all of these docs at once.

[samuelsycamore]

Re: this comment from @michaldudak, I am going to move the Unstyled components page to the Base docs and split it up into a few "Getting started" pages.

[samuelsycamore]

Template for re-formatting these pages after the first round of revisions is merged:

 ## Introduction
 ## Components API
 ### Component only content
 ## Hooks
 ### Hooks only content

[samuelsycamore]

Note to self: HTML tags like <code> in the description <p> don't play nicely with search engines. These will need to be removed in the final pass.

[samuelsycamore]

Several pages such as the Switch doc mention the shared components / component / componentsProps props. The main component itself is called the "owner." We can link to more info about these props after #32562 is merged.

Similarly, we can link to the section about "Components vs hooks" from the new Usage page on the docs for components that have hook counterparts.

[samuelsycamore]

ClickAwayListener needs to be reverted to its old title for SEO purposes. See: this comment

[samuelsycamore]

We need to come to a consensus about styling component names, and when to refer to a specific component vs its general usage. See: this discussion

[michaldudak]

IMO we can use just the capitalized component name without backticks unless we instruct the reader to type it or show how it should look in the code (with angle brackets) - so ButtonUnstyled and <ButtonUnstyled />.

I'd keep the backticks whenever we refer to a prop, though.

[samuelsycamore]

The first pass is now complete for all Base docs! 🙌 My next task will be to create a PR that addresses formatting inconsistencies across all of these pages at once.

[samuelsycamore]

There will always be further improvements to make, but I believe that the scope of this Issue has been resolved now that #33156 is merged.