[List] Add support for list item container style overrides

[mnajdova]

This PR adds the support for adding style overrides for the container inside the ListItem.

Also fixes #25774

[mui-pr-bot]

Details of bundle changes

Generated by 🚫 dangerJS against e174ced

[oliviertassinari]

In #13597 we discuss changing the structure. Basically, it's not OK to change the root dynamically (since v1). It's magical. Does taking this issue into account, and more specifically the flattening direction change the outcome of this PR?

I mean, was:

diff --git a/packages/material-ui/src/ListItem/ListItem.js b/packages/material-ui/src/ListItem/ListItem.js
index d06a7edc18..ae25d6df7b 100644
--- a/packages/material-ui/src/ListItem/ListItem.js
+++ b/packages/material-ui/src/ListItem/ListItem.js
@@ -151,7 +151,7 @@ const ListItemContainer = experimentalStyled(
   {
     name: 'MuiListItem',
     slot: 'Container',
-    overridesResolver,
+    overridesResolver: (props, styles) => styles.container,
   },
 )({
   position: 'relative',

considered as an option for the solution?

[mnajdova]

In #13597 we discuss changing the structure. Basically, it's not OK to change the root dynamically. It's magical. Does taking this issue into account, and more specifically the flattening direction change the outcome of this PR?

I mean, was:

index d06a7edc18..ae25d6df7b 100644
--- a/packages/material-ui/src/ListItem/ListItem.js
+++ b/packages/material-ui/src/ListItem/ListItem.js
@@ -151,7 +151,7 @@ const ListItemContainer = experimentalStyled(
   {
     name: 'MuiListItem',
     slot: 'Container',
-    overridesResolver,
+    overridesResolver: (props, styles) => styles.container,
   },
 )({
   position: 'relative',

considered as an option for the solution?

I haven't thought of this, mainly because it kind of validates the CSS structure that I had in mind. My thinking was that it is unintuitive to define styles in a component that is a child of another. On the other hand, we won't have breaking changes with the proposed fix, plus it doesn't require the developers to have knowledge of the internal structure of the component. Let me update.