[Modal][material] Fix console warning when onTransitionEnter , onTransitionExit provided

[sai6855]

closes: #38843

before: https://codesandbox.io/s/mui-swipabledrawer-example-new-7pnch2

after: https://codesandbox.io/s/affectionate-hooks-vwlqrk

Base Modal extracted onTransitionEntered, onTransitionExited here from props before passing to useSlotProps here. That's why same error didn't occured in BaseUI Modal. This PR follows same implemetation as BaseUI Modal to fix the warning

• I have followed (at least) the PR section of the contributing guide.

[mui-bot]

Netlify deploy preview

https://deploy-preview-38868--material-ui.netlify.app/

Bundle size report

Details of bundle changes (Toolpad)
Details of bundle changes

Generated by 🚫 dangerJS against b2d20f0

[mnajdova]

Nice catch. We make sure they are not spread when using the getRootProps callback, but here they are spread as part of the other. One more benefit of being able to send all props to the getSlotProps callbacks - we can intercept props that should not be propagated further cc @mj12albert

[DiegoAndai]

Thanks for jumping into this one @sai6855! 🎉

[mnajdova]

@sai6855 this pull request was a duplicate of #38745. For more trivial fixes, we can allow first-time contributors or some contributors that are not that active to pick them up. It would have been much better if you'd reviewed the other pull request, rather than creating the pull request yourself. A note for next time - check if there is an ongoing pull request and link it with the original issue - this will help with not picking up duplicate work.

[sai6855]

@sai6855 this pull request was a duplicate of #38745. For more trivial fixes, we can allow first-time contributors or some contributors that are not that active to pick them up. It would have been much better if you'd reviewed the other pull request, rather than creating the pull request yourself. A note for next time - check if there is an ongoing pull request and link it with the original issue - this will help with not picking up duplicate work.

Oh, since PR wasn't linked to the issue I wasn't aware of that pr . If it was linked i wouldn't touch the issue or create new PR. Also PR was opened before issue was created so there is very little chance that i would be aware of that PR. But from next time i'll be bit more careful