chore(deps) Update dependency @semantic-release/npm to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/npm	9.0.2 -> 10.0.2

---

Release Notes

semantic-release/npm

v10.0.2

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v11.1.1 (#​591) (31e0e27)

v10.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v7 (#​575) (4c11706)

v10.0.0

Compare Source

Bug Fixes

• aggregate-error: upgraded to the latest version (7285e05)
• deps: upgraded npm to v9 (2a79f80)
• execa: upgraded to the latest version (7c74660)
• normalize-url: upgraded to the latest version (b55bb01)
• remove support for legacy auth (51ab3c8)
• tempy: upgraded to the latest version of tempy (f1992a5)

Code Refactoring

• esm: converted the package to esm (2d8ff15)

Features

• node-versions: dropped support for node versions below v18 (aff3574)
• semantic-release-peer: raised the minimum peer requirement to the first version that supports loading esm plugins (22e70ad)

BREAKING CHANGES

• deps: the direct dependency on npm has been upgraded to v9. details of breaking changes
  can be found at https://github.com/npm/cli/releases/tag/v9.0.0
• semantic-release-peer: the required version of semantic-release has been
  raised to v20.1.0 in order to support loading of ESM plugins
• aggregate-error: due to the aggregate-error upgrade, thrown errors are no longer iterable, but instead list the errors under an errors property
• legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
• node-versions: node v18 is now the minimum required node version
• esm: @semantic-release/npm is now a native ES Module. It
  has named exports for each plugin hook (verifyConditions, prepare,
  publish, addChannel)

---

Configuration

📅 Schedule: Branch creation - "before 8am on Monday" in timezone America/Chicago, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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, check this box

---

This PR has been generated by Mend 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 click 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: package-lock.json

npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.6.3
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.3>
npm notice Run `npm install -g npm@9.6.3` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: atlas_bi_library@undefined
npm ERR! Found: semantic-release@19.0.5
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"19.0.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=20.1.0" from @semantic-release/npm@10.0.2
npm ERR! node_modules/@semantic-release/npm
npm ERR!   dev @semantic-release/npm@"10.0.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-04-03T21_03_16_321Z-debug-0.log

[github-advanced-security]

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.