[code-infra] Fix failing Netlify build

[cherniavskii]

After experimenting with different things in #13623 (you can see my commits if you're curious about what I tried), I managed to have the Netlify build working again.

I don't know what the origin of the issue is and why it's not reproducible locally after clearing the cache.

Testing:

• I tested it in 56f5131 (#13623) and it fixed the failing build.
• The ultimate test for this would be merging this PR and then merging master into one of the PRs that has the build failing

Other attempts

• ❌ Make sure the correct version of @mui/joy installed on Netlify. Commit Deployment
• ❌ Remove Next.js build cache before build (docs/.next) Commit Deployment
• ❌ Merge the latest master. Commit Deployment
• ❌ Bump a dependency to update the lockfile and invalidate the old cache Commit Deployment
• ❌ Downgrade pnpm version.
  • 9.4.0 Commit Deployment
  • 9.3.0 Commit Deployment

[mui-bot]

Deploy preview: https://deploy-preview-14104--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 55e6232

[JCQuintas]

Did you have to do any change on @mui/monorepo/docs/pages/_document or it was simply copy/paste?

[cherniavskii]

@JCQuintas It's pure copy/paste from the latest next branch of the monorepo, not a single character changed:
https://github.com/mui/material-ui/blob/f9de2dd508b59623a99949f8891b96cf0016581c/docs/pages/_document.js

[LukasTy]

It looks like our Netlify config might not be ideal based on their doc and the following points from.

5. If you are using yarn workspaces 14 or a monorepo 16 please consult the appropriate documentation (linked to in this sentence).
6. Fairly rare but worth mentioning: You have a package.json in your repo root, but you are building a subdirectory of your repo and have NOT appropriately set the base directory in your build settings. That can lead to some confusing caching situations since we’ll only sometimes use that package.json (when there is nocache).

WDYT about trying this approach? 🤔
#14105