Bump fs-extra to ^11.1.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fs-extra	^10.1.0 -> ^11.1.1
@types/fs-extra (source)	^9.0.13 -> ^11.0.1

---

Release Notes

jprichardson/node-fs-extra (fs-extra)

v11.1.1

Compare Source

• Preserve timestamps when moving files across devices (#​992, #​994)

v11.1.0

Compare Source

• Re-add main field to package.json for better TypeScript compatibility (#​979, #​981)

v11.0.0

Compare Source

Breaking Changes

• Don't allow requiring fs-extra/lib/SOMETHING (switched to exports) (#​974)
• Require Node v14.14+ (#​968, #​969)

New Features

• Add fs-extra/esm for ESM named export support; see docs for details (#​746, #​974)
• Add promise support for fs.readv() (#​970)

Bugfixes

• Don't stat filtered items in copy* (#​965, #​971)
• Remove buggy stats check in copy (#​918, #​976)

---

Configuration

📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[mui-bot]

Netlify deploy preview

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

Bundle size report

No bundle size changes

Generated by 🚫 dangerJS against 4709857

[michaldudak]

LGTM. @siriwatknp would you mind being the second reviewer (it's a major version bump)?

[DiegoAndai]

@michaldudak a question regarding the support for Node 12 being dropped and the packages we use it in

• The material (for tests), icons-material (for build), and netlify-plugin-cache-docs packages all use fs-extra but specify "node": ">=12.0.0 under package.json > engines, would we need to specify Node v14.14+?
• The benchmark, api-docs-builder, and mui-envinfo packages, as well as the scripts, tests/regression, and tests/utils folders all use fs-extra, could there be a problem if we don't specify support for Node v14.14+?
• The docs package is in the clear as it uses NextJS v13 which uses Node v14.18

[michaldudak]

The engines field describes the node version we support for installing our packages (i.e., you currently can't npm install @mui/material under Node 10. fs-extra is not used in production code, so it's safe to still have Node 12 there.