[pickers] Fix transformOrigin resolving based on popper placement

[LukasTy]

Fix the resolving of transformOrigin here:

mui-x/packages/x-date-pickers/src/internals/components/PickerPopper/PickerPopper.tsx

Lines 117 to 120 in 6e70d48

	props: ({ popperPlacement }) => new Set(['top', 'top-start', 'top-end']).has(popperPlacement),
	style: {
	transformOrigin: 'bottom center',
	},

ownerState always included the initial value of placement, regardless of the provided one.
This lead to the following problem:

Before

Screen.Recording.2025-06-03.at.16.26.36.mov

After

Screen.Recording.2025-06-03.at.16.26.58.mov

[mui-bot]

Deploy preview: https://deploy-preview-18206--material-ui-x.netlify.app/

Bundle size report

Total Size Change:^{${\tiny{\color{red}▲}}$}+602B^(0.00%) - Total Gzip Change:^{${\tiny{\color{red}▲}}$}+149B^(0.00%)
Files: 120 total (0 added, 0 removed, 14 changed)

Show 14 more bundle changes

@mui/x-date-pickers parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.02%) gzip:^{${\tiny{\color{red}▲}}$}+19B^(+0.03%)
@mui/x-date-pickers-pro parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.01%) gzip:^{${\tiny{\color{red}▲}}$}+6B^(+0.01%)
@mui/x-date-pickers-pro/DateRangePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.02%) gzip:^{${\tiny{\color{red}▲}}$}+9B^(+0.02%)
@mui/x-date-pickers-pro/DateTimeRangePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.02%) gzip:^{${\tiny{\color{red}▲}}$}+5B^(+0.01%)
@mui/x-date-pickers-pro/DesktopDateRangePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.03%) gzip:^{${\tiny{\color{red}▲}}$}+8B^(+0.02%)
@mui/x-date-pickers-pro/DesktopDateTimeRangePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.02%) gzip:^{${\tiny{\color{red}▲}}$}+19B^(+0.03%)
@mui/x-date-pickers-pro/DesktopTimeRangePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.03%) gzip:^{${\tiny{\color{red}▲}}$}+10B^(+0.02%)
@mui/x-date-pickers-pro/TimeRangePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.03%) gzip:^{${\tiny{\color{red}▲}}$}+11B^(+0.03%)
@mui/x-date-pickers/DatePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.03%) gzip:^{${\tiny{\color{red}▲}}$}+10B^(+0.02%)
@mui/x-date-pickers/DateTimePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.02%) gzip:^{${\tiny{\color{red}▲}}$}+10B^(+0.02%)
@mui/x-date-pickers/DesktopDatePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.03%) gzip:^{${\tiny{\color{red}▲}}$}+8B^(+0.02%)
@mui/x-date-pickers/DesktopDateTimePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.02%) gzip:^{${\tiny{\color{red}▲}}$}+7B^(+0.01%)
@mui/x-date-pickers/DesktopTimePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.03%) gzip:^{${\tiny{\color{red}▲}}$}+6B^(+0.02%)
@mui/x-date-pickers/TimePicker parsed:^{${\tiny{\color{red}▲}}$}+43B^(+0.03%) gzip:^{${\tiny{\color{red}▲}}$}+21B^(+0.05%)

Details of bundle changes

Generated by 🚫 dangerJS against db983cc

[LukasTy]

To have the final popperPlacement value here, we would need to resolve the slotProps.popper twice. 🙈
I opted for a slight BC by removing this field from the type to avoid inconsistencies or ugly and less performant code. 🙈

[flaviendelangle]

Not great but fine doing it :/

[flaviendelangle]

Not great but fine doing it :/