Update dependency fs-extra to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fs-extra	^8.0.0 -> ^10.0.0

---

Release Notes

jprichardson/node-fs-extra

v10.1.0

Compare Source

• Warn if fs.realpath.native does not exist, instead of erroring (#​953)
• Allow explicitly passing undefined options to move() (#​947, #​955)
• Use process.emitWarning instead of console.warn (#​954)

v10.0.1

Compare Source

• Add sideEffects: false to package.json (#​941)

v10.0.0

Compare Source

Breaking changes

• Require Node.js v12+ (#​886, #​893, #​890, #​894, #​895)
• Allow copying broken symlinks (#​779, #​765, #​638, #​761)

The following changes, although technically semver-major, will not affect the vast majority of users:

• Ensure correct type when destination exists for ensureLink*()/ensureSymlink*() (#​826, #​786, #​870)
• Error when attempting to copy*() unknown file type (#​880)
• Remove undocumented options for remove*() (#​882)

Improvements

• Allow changing case of filenames with move*(), even on technically case-insensitive filesystems (#​759, #​801)
• Use native fs.rm*() for remove*() in environments that support it (#​882, #​806)
• Improve emptyDir() performance (#​885)

Bugfixes

• Ensure copy*()'s filter function is not called more than necessary (#​883, #​809)
• Fix move*() raising EPERM error when moving a file to the root of a drive on Windows (#​897, #​819)

Miscellaneous changes

• Do not use at-least-node as a dependency (#​896)
• Improve documentation (#​888, #​830, #​884, #​843)

v9.1.0

Compare Source

• Add promise support for fs.rm() (#​841, #​860)
• Upgrade universalify for performance improvments (#​825)

v9.0.1

Compare Source

• Fix issue with ensureFile() when used with Jest on Windows (#​804, #​805)
• Remove unneeded process.umask() call (#​791)
• Docs improvements (#​753, #​795, #​797)

v9.0.0

Compare Source

Breaking changes

• Requires Node.js version 10 or greater (#​725, #​751)
• Switched ensureDir* to use a fork of https://github.com/sindresorhus/make-dir to make use of native recursive fs.mkdir where possible (#​619, #​756)
• Properly preserve atime for copy* with preserveTimestamps option (#​633)

The following changes, allthough technically breaking, will not affect the vast majority of users:

• outputJson now outputs objects as they were when the function was called, even if they are mutated later (#​702, #​768)
• Cannot pass null as an options parameter to *Json* methods (#​745, #​768)

Improvements

• Add promise shims for fs.writev & fs.opendir (#​747)
• Better errors for ensureFile (#​696, #​744)
• Better file comparison for older Node versions (#​694)

Miscellaneous changes

• Peformance optimizations (#​762, #​764)
• Add missing documentation for aliases (#​758, #​766)
• Update universalify dependency (#​767)

---

Configuration

📅 Schedule: 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 this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

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

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://registry.npmjs.org/yarn
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-07-06T10_04_52_751Z-debug.log