feat: deprecate "waitUntilReady" (deferNetworkUntil) worker option

[kettanaito]

• Fixes MSW doesn't restore fetch is the worker is stopped before "deferNetworkRequestUntil" resolves #1573
• Closes fix(deferNetworkUntil): restore module patches on registration rejections #1865
• Closes fix(deferNetworkUntil): enable mocking when no pendingWorker #1906

This removes the deferNetworkUntil functionality altogether. It's been introduced in the past to support use cases when developers ran worker.start() and their application rendering in parallel. This has since been discouraged. You must defer your application's rendering to eliminate any race conditions between the worker registration and any requests your app makes on the initial render. The default recommended browser integration also encourages that in the docs.

[kettanaito]

Marking this as a minor version bump to be safe. There are no breaking changes for those not using the waitUntilReady options. For those using it, the deprecation warning suggests how to migrate to the deferred application rendering scenario by linking to the docs. The deferNetworkUntil functionality itself introduced a bunch of issues that went unnoticed, which makes me believe there's a small percentage of people actually using that option.

[kettanaito]

Released: v2.1.0 🎉

This has been released in v2.1.0!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.