[pickers] Remove WrapperVariantContext from DateTimePickerTabs

[LukasTy]

Part of #7372

[mui-bot]

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

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	616.8	1,079.4	643.5	795.26	191.922
Sort 100k rows	ms	686.1	1,296.6	869.7	950.02	199.822
Select 100k rows	ms	204.3	394.9	237.3	267.22	68.426
Deselect 100k rows	ms	149.6	303.9	184.6	220.76	60.482

Generated by 🚫 dangerJS against fdcf78e

[flaviendelangle]

Couldn't we handle the styling at the PickersLayoutContentWrapper level ?
Set flexDirection: 'column-reverse' and set the shadow there or change the rendering order (depending on what keyboard order we want).

Because with the current approach, PickersLayout handled all the positioning and the tabs say "no no I do want to be below"

[LukasTy]

Couldn't we handle the styling at the PickersLayoutContentWrapper level ?

We probably could, but that was not the intent of this PR.
I'll look into this option as it could probably be even more clean solution if we could use layout and avoid the need for wrapperVariant on the tabs. 😃 👍

[flaviendelangle]

As soon as we have the satisfies instead of the type casting I'm good with merging 👍

[LukasTy]

As soon as we have the satisfies instead of the type casting

I initially did not notice the compilation error. I'm trying to understand why it might be failing to compile on our codebase, even though we have most of the latest libraries. 🤔
https://stackoverflow.com/questions/74677993/typescript-react-app-is-throwing-error-when-using-the-new-satisfies-operator-w