[system] Fix changed types between 5.14.0 and 5.14.1

[gitstart]

Description

Update the styled component typing to include component prop typing.

closes #38626

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

---

This code was written and reviewed by GitStart Community. Growing great engineers, one PR at a time.

[mui-bot]

Netlify deploy preview

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

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 36ba47a

[gitstart]

@DiegoAndai this PR is ready for review

[DiegoAndai]

Hey @gitstart, this is the same PR as https://github.com/mui/material-ui/pull/39288/files, which was closed. We should continue the discussion in that original PR unless there's a reason not to. There's a question I made regarding the root cause of the bug.

[gitstart]

Hey @gitstart, this is the same PR as https://github.com/mui/material-ui/pull/39288/files, which was closed. We should continue the discussion in that original PR unless there's a reason not to. There's a question I made regarding the root cause of the bug.

Hi @DiegoAndai, due to some internal cleanups on our end, we had to refork the repo which caused the previously pushed PRs to become permanently closed, unfortunately. However, we would be happy to continue the discussion on this PR.

[DiegoAndai]

@gitstart ok, the context for the discussion is in #39288 then, and we left of in the following question from my side:

Why this change made the RootComponent become the second argument? I tested and removing & { component?: React.ElementType; } made this bug disappear. So, is the RootComponent argument supposed to be there? Or should we fix it because it shouldn't? If it is correct for RootComponent to be the third argument, we should probably update all three types on CreateMUIStyled that use forwarded props as the second argument, as that should be the third, right?

[ZeeshanTamboli]

As the PR is inactive, I am closing it.