chore(dev dependencies): update dependency @testing-library/dom to v8

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/dom	7.31.2 -> 8.0.0

---

Release Notes

testing-library/dom-testing-library

### [`v8.0.0`](https://togithub.com/testing-library/dom-testing-library/releases/v8.0.0) [Compare Source](https://togithub.com/testing-library/dom-testing-library/compare/v7.31.2...v8.0.0) ##### Recommendations 1. If you're using `jest` fake timers make sure you use modern timers jest 27: ```diff -jest.useFakeTimers('legacy') +jest.useFakeTimers('modern') // jest.config.js -"timers": "legacy", +"timers": "modern", ``` jest 26: ```diff -jest.useFakeTimers() +jest.useFakeTimers('modern') // jest.config.js -"timers": "legacy", +"timers": "modern", ``` ##### chore - Release v8 as stable ([#​979](https://togithub.com/testing-library/dom-testing-library/issues/979)) ([d347302](https://togithub.com/testing-library/dom-testing-library/commit/d347302d6b17280b71505d55d0cb9cda376b95cc)) ##### BREAKING CHANGES - Remove deprecated `waitFormDOMChange` - Remove deprecated `waitForElement` - The `timeout` in `waitFor(callback, { interval, timeout } )` now uses the same clock as `interval`. Previously `timeout` was always using the real clock while `interval` was using the global clock which could've been mocked out. For the old behavior I'd recommend `waitFor(callback, { interval, timeout: Number.POSITIVE_INFINITY })` and rely on your test runner to timeout considering real timers. - ` Githubissues.

Githubissues is a development platform for aggregating issues.