[POC] Configure setting ownerState on slots

[michaldudak]

DO NOT MERGE

This is a playground that illustrates an alternative way of accessing ownerState in slot components.
A SwitchUnstyled is used for this example.

Related issue: #32882

This is one of the possible solutions. The other one is described in #35654.

A new prop was added to SwitchUnstyled - provideOwnerStateToSlots. It controls whether ownerState is passed as a prop to slot components. Developers can set this prop when they intend to make rendering of a slot dependent on the state of the owner component (as shown in this PR and on the linked codesandbox). The prop would be set to false (or not set) when slot components don't expect ownerState in props. This will be especially useful when using 3rd party components as slots (for example React Router's Link as a root slot of a Button).

Advantages over the existing API:

1. 3rd party components can be used in slots without wrapping them in custom code that strips out the ownerState from props.
2. Potentially better performance than [POC] ownerState access: use context #35654

Disadvantages:

1. Low granularity - the prop doesn't work per slot, but on the whole component. If one slot require customisation using ownerState and the other is a 3rd party component, they will require additional code to work together.
2. Low discoverability - it is not immediately obvious why slot components don't work with ownerState out of the box
3. Another prop to support on all components

Playgrounds

New API: https://codesandbox.io/s/recursing-turing-8m5yvj?file=/src/App.tsx

Existing API: https://codesandbox.io/s/confident-hermann-q1kiwf?file=/src/App.tsx

[mui-bot]

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

Details of bundle changes

Generated by 🚫 dangerJS against e287f68

[mnajdova]

I don't think we should consider this alternative to #35654 as it is not as granular as the other one. If we add this option per slot that would be a clear mapping of the functionalities.

[michaldudak]

We could have something like:

<SwitchUnstyled slots={slots} slotConfig={{ thumb: { provideOwnerState: true } }} />

I've created a sandbox in #35668.

[mnajdova]

<SwitchUnstyled slots={slots} slotConfig={{ thumb: { provideOwnerState: true } }} />

I was thinking more of allowing people to add them in the slotProps and intercept the provideOwnerState prop in the unstyled component. Something more towards:

<SwitchUnstyled slots={slots} slotProps={{ thumb: { provideOwnerState: true } }} />

[michaldudak]

Closing in favor of #35668