fix(deps): update dependency @testing-library/jest-dom to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/jest-dom	^5.16.4 -> ^6.0.0

---

Release Notes

testing-library/jest-dom (@​testing-library/jest-dom)

v6.1.4

Compare Source

Bug Fixes

• upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#​532) (44f1eab)

v6.1.3

Compare Source

Bug Fixes

• proper @​jest/globals import (#​530) (5b492ac)

v6.1.2

Compare Source

Bug Fixes

• bump @​adobe/css-tools for ESM support (#​525) (b959a68)

v6.1.1

Compare Source

Bug Fixes

• package.json: update main and module file paths (#​523) (853a3e5)

v6.1.0

Compare Source

Features

• Publish ESM and CJS (https://github.com/testing-library/jest-dom/pull/519)

v6.0.1

Compare Source

Bug Fixes

• matchers type is making the global expect unsafe (#​513) (bdb34f1)

v6.0.0

Compare Source

Features

• local types, supporting jest, @​jest/globals, vitest (#​511) (4b764b9)

BREAKING CHANGES

• Removes the extend-expect script. Users should use
  the default import path or one of the new test platform-specific
  paths to automatically extend the appropriate "expect" instance.

extend-expect was not documented in the Readme, so this change should
have minimal impact.

Users can now use the following import paths to automatically extend
"expect" for their chosen test platform:

• @​testing-library/jest-dom - jest (@​types/jest)
• @​testing-library/jest-dom/jest-globals - @​jest/globals
• @​testing-library/jest-dom/vitest - vitest

For example:

import '@​testing-library/jest-dom/jest-globals'

Importing from one of the above paths will augment the appropriate
matcher interface for the given test platform, assuming the import
is done in a .ts file that is included in the user's tsconfig.json.

It's also (still) possible to import the matchers directly without
side effects:

import * as matchers from '@​testing-library/jest-dom/matchers'

• Update kcd-scripts
• Drop node < 14

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, 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 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: test-apps/cra-e2e-and-ct/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @testing-library/[email protected]
npm ERR! Found: @types/[email protected]
npm ERR! node_modules/@types/jest
npm ERR!   @types/jest@"^27.5.2" from the root project
npm ERR!   @types/jest@"*" from @types/[email protected]
npm ERR!   node_modules/@types/testing-library__jest-dom
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/jest@">= 28" from @testing-library/[email protected]
npm ERR! node_modules/@testing-library/jest-dom
npm ERR!   @testing-library/jest-dom@"^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @types/[email protected]
npm ERR! node_modules/@types/jest
npm ERR!   peerOptional @types/jest@">= 28" from @testing-library/[email protected]
npm ERR!   node_modules/@testing-library/jest-dom
npm ERR!     @testing-library/jest-dom@"^6.0.0" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/44b680/12127e/cache/others/npm/_logs/2023-10-15T17_45_09_026Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/44b680/12127e/cache/others/npm/_logs/2023-10-15T17_45_09_026Z-debug-0.log

[cypress-app-bot]

See the guidelines for reviewing dependency updates for info on how to review dependency update PRs.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.