[pickers] Fix broken ref forwarding

[oliviertassinari]

So developers get less noise, so they can focus on the important messages. We didn't test #32950 in depth.

Sample test:

import * as React from 'react';
import TextField from '@mui/material/TextField';
import { AdapterDateFns } from '@mui/x-date-pickers/AdapterDateFns';
import LocalizationProvider from '@mui/lab/LocalizationProvider';
import DatePicker from '@mui/lab/DatePicker';

export default function BasicDatePicker() {
  const [value, setValue] = React.useState<Date | null>(null);

  return (
    <LocalizationProvider dateAdapter={AdapterDateFns}>
      <DatePicker
        label="Basic example"
        value={value}
        onChange={(newValue) => {
          setValue(newValue);
        }}
        renderInput={(params) => <TextField {...params} />}
      />
    </LocalizationProvider>
  );
}

Before

After

[mui-bot]

Details of bundle changes

Generated by 🚫 dangerJS against fedbf00

[oliviertassinari]

Oh, I didn't know that #33085 and #33080 existed.

For context, my process to work on this was about 1.:

1. I wanted to try [core] Remove dead and redundant code #33125 out.
2. I noticed we had a warning in the console, so I was like, well, why not fix it: [Grid] Fix prop-type key regression #33123
3. Doing such, I noticed that the date picker had a key prop generated, so I tried it out. I could reproduce
4. I found this bug, so I fixed it [pickers] Fix broken ref forwarding #33107
5. I have found 2-3 more problems but I stopped there, I only took notes about them. I would have spent my whole weekend coding otherwise 😁