[core] Extract classes descriptions from TypeScript

[eps1lon]

Will not remove the runtime classes descriptions in this PR for reviewability. I'll remove them in a follow-up.

Originally we extracted these descriptions from the runtime code e.g.

export const styles = {
  /* Styles applied to the root element */
  root: {}
}

For components using emotion that approach no longer worked. Instead, we parsed the AST of the TypeScript declaration files.

Relying on the AST is generally brittle since it breaks every time we change the pattern. Instead, we can rely on the TS type-checker (can re-use typescript-to-proptypes resulting in a significantly simpler docs:api implementation). This has the benefit of giving us a single approach that doesn't care about where the classes are located. It will document the same thing a dev will see when writing the code and looking at IntelliSense.

This revealed a couple of excess declared classes that have no effect at runtime (#25917) and missing classes (upcoming PR). You'll notice these issues in the current state of the PR.

Requires #25917
Required for #25754

[mui-pr-bot]

No bundle size changes (experimental)

Generated by 🚫 dangerJS against 9959ce6

[eps1lon]

Better failure message due to displaying a diff. include does not "include" a diff in the failure message.

[eps1lon]

Merging since there isn't much any changes to the documentation (the order for internal pickers components are for now ignored).