[docs] Improve API for theme default prop

[oliviertassinari]

I initially only wanted to remove logic related to a given open-source project from the ApiPage so we can keep it more generic, e.g.

material-ui/docs/src/modules/components/ApiPage.js

Line 303 in f71821e

{(componentStyles.name || isJoyComponent) && (

there shouldn't be project specific logic like this, it's way too specific when it can be inside the json.

But then, I went a bit above to differentiate default prop customization to style customization. These are implemented differently now, especially with the data grid.

Before:

• https://mui.com/material-ui/api/card/#component-name
• https://mui.com/joy-ui/api/card/#component-name

After:

• https://deploy-preview-36490--material-ui.netlify.app/material-ui/api/card/#component-name
• https://deploy-preview-36490--material-ui.netlify.app/joy-ui/api/card/#component-name

[mui-bot]

Netlify deploy preview

• docs/data/joy/customization/themed-components/themed-components.md
• docs/data/material/components/about-the-lab/about-the-lab.md
• docs/data/material/components/alert/alert.md
• docs/data/material/components/use-media-query/use-media-query.md
• docs/data/material/customization/theme-components/theme-components.md

@material-ui/core: parsed: +Infinity% , gzip: +Infinity%
@material-ui/lab: parsed: +Infinity% , gzip: +Infinity%
@material-ui/styles: parsed: +Infinity% , gzip: +Infinity%
@material-ui/private-theming: parsed: +Infinity% , gzip: +Infinity%
@material-ui/system: parsed: +Infinity% , gzip: +Infinity%
@material-ui/unstyled: parsed: +Infinity% , gzip: +Infinity%
@material-ui/utils: parsed: +Infinity% , gzip: +Infinity%
@mui/material-next: parsed: +Infinity% , gzip: +Infinity%
@mui/joy: parsed: +Infinity% , gzip: +Infinity%

Bundle size report

Details of bundle changes

Generated by 🚫 dangerJS against 0b531a4

[oliviertassinari]

Follow-up thoughts:

1. Shouldn't root be at the top: https://deploy-preview-36490--material-ui.netlify.app/joy-ui/api/button/#slots? [docs] Keep slot code order in API docs #36499
2. JoyButton is a bit strange to customize the default when the class name is MuiButton. IMHO, the correct way to handle this here is to isolate the emotion context between Joy UI and Material UI & use MuiButton.
3. We miss the docs for the component prop in https://deploy-preview-36490--material-ui.netlify.app/joy-ui/api/alert/#props.
4. In the card https://deploy-preview-36490--material-ui.netlify.app/joy-ui/api/card/, we have no docs about the root element class name. Should we?
5. The className for the input slot is wrong in https://deploy-preview-36499--material-ui.netlify.app/base/api/slider-unstyled/#slots, it doesn't exist, and probably shouldn't
6. Related to 4. we have no docs about the custom class names in https://deploy-preview-36499--material-ui.netlify.app/base/api/slider-unstyled/ like we have in https://deploy-preview-36499--material-ui.netlify.app/material-ui/api/slider/#css, shouldn't we?

[hbjORbj]

(1) I opened a PR (#36519) for this today (didn't know you opened a PR for it already!). I think we can go with your PR.

(3) I will handle this.

(4) I think we should. I can take of this. #36540

(5) I will handle this. #36539

(6) cc @michaldudak @siriwatknp

[hbjORbj]

@oliviertassinari
(3) I noticed that component, slots, slotProps are missing in API docs of some components of all Base, Material and Joy. Were we aware of this?

For example, PopperUnstyled is missing component, and Material UI Avatar is missing slots and slotProps.

EDIT: Base components will no longer have component prop (Marija will work on this, I think).

[siriwatknp]

For (6), I think we can extract the description and put it above the table (in a separate PR). This will also fix #36328 (comment).