[docs] Disallow undefined array members at runtime where they're unexpected

[eps1lon]

TL;DR: Refactor to make dynamic props table easier to generate that revealed a bug where <Hidden only={[undefined]} /> did not warn at runtime.

Original goal was to do a big refactor of typescript-to-proptypes away from a single generate function and the "branded-nodes-everywhere" approach (see typeString and type-guards).

typescript-to-proptypes will be re-purposed to create an intermediary data structure that is used to build the API docs and propTypes (currently TS -> propTypes -> docs, new: TS -> struct, struct -> propTypes, struct -> docs). The intermediary data structure is intended as a generic API which we want to minify. Branding is unnecessary in most cases (structural typing is sufficient). Using propTypes as a public API also has its drawbacks when it comes to module augmentation. E.g. in Button we need a custom validator for variant (see #21648) but our docs can safely be generated from typescript.

The single generate function was also hard to reason about. We now have dedicated functions for each structure with a single purpose where before some branches where responsible for Components and union nodes. Checking if a prop is required is a bit more convoluted but I'm confident we can simplify this even more.

[mui-pr-bot]

No bundle size changes comparing abfd06b...534687e

Generated by 🚫 dangerJS against 534687e

[oliviertassinari]

typescript-to-proptypes will be re-purposed to create an intermediary data structure that is used to build the API docs and propTypes (currently TS -> propTypes -> docs, new: TS -> struct, struct -> propTypes, struct -> docs).

@eps1lon It sounds like a great direction :)