[System] Calls unstable_createStyleFunctionSx with passed in arg

[CalebJamesStevens]

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

What does this fix

The purpose of this PR is to fix compatibility issues with turbopack for next.js 13. The issue can be found in this open issue

Fixes #34910

What changes were made to fix this

For uknown reasons unstable_createStyleFunctionSx on line 98 was not able to grab the import to use as a default on its own when ran with turbopack bundler causing a reference error shown in git issue link above

[mui-bot]

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

Details of bundle changes

Generated by 🚫 dangerJS against f431097

[CalebJamesStevens]

I don't know how to add a label i'm sorry. Been looking for a long time now and i'm getting tired.

[Duoquote]

Any updates on this?

[CalebJamesStevens]

Any updates on this?

Made the PR last night but don't know how to add labels to the PR so idk if they'll even look at it

[Kliton]

Any update?

[CalebJamesStevens]

Any update?

Still waiting, soon possibly

[CalebJamesStevens]

Anyone going to review this...?

[mnajdova]

For uknown reasons unstable_createStyleFunctionSx on line 98 was not able to grab the import to use as a default on its own when ran with turbopack bundler causing a reference error shown in git issue link above

We should work on finding out the reason for this. I don't think it's related to MUI, or at least it's not clear why it happens on this specific import. Note that the turbopack is still in alpha, so creating an issue on their repo is more likely to guide us to the reason of why this happens. I can't imagine lots of library changing their code, just because some import is not picked up by turbopack.

I am mainly saying this, because we could write a similar code tomorrow, that would break the build again.