chore(deps): update dependency nock to v13

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
nock	devDependencies	major	12.0.3 -> 13.0.2

---

Release Notes

nock/nock

v13.0.2

Compare Source

Bug Fixes

• intercept: mark Interceptors consumed immediately (#​2033) (3b24821)

v13.0.1

Compare Source

Bug Fixes

• allow Content-Type request introspection when header is an array (#​2010) (e432ac5), closes #​2009

v13.0.0

Compare Source

See the Migration Guide

Breaking changes

1. Scope.log has been removed. Use the debug library when debugging failed matches.

2. socketDelay has been removed. Use delayConnection instead.

3. delay, delayConnection, and delayBody are now setters instead of additive.

4. When recording, skipping body matching using * is no longer supported by nock.define.
   Set the definition body to undefined instead.

5. ClientRequest.abort() has been updated to align with Node's native behavior.
   This could be considered a feature, however, it created some subtle differences that are not backwards compatible. Refer to the migration guide for details.

6. Playback of a mocked responses will now never happen until the 'socket' event is emitted.

---

Renovate configuration

📅 Schedule: "before 3am on Friday" (UTC).

🚦 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 WhiteSource Renovate. View repository job log here.

[obecny]

it looks like socketDelay has been removed from nock in favour of delayConnection so the upgrade to v13 is not possible without changing the code (although not sure if this is the only change) @mayurkale22 what do you usually do in such situation ?

[mayurkale22]

it looks like socketDelay has been removed from nock in favour of delayConnection so the upgrade to v13 is not possible without changing the code (although not sure if this is the only change) @mayurkale22 what do you usually do in such situation ?

In case of devdependencies, I just close the PR. Ideally, we should open an issue and close the PR to address it later.

[obecny]

closing and opening a new issue to make it manually
#1303

[forking-renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 13.x releases. However, if you upgrade to 13.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.