chore(deps): update dependency nock to v10

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	References
nock	devDependencies	major	^9.2.6 -> ^10.0.0	source

---

Release Notes

nock/nock

v10.0.4

Compare Source

Bug Fixes

• #​1266: throw useful error if "method" parameter is not set for .intercept() – thanks @​labsvisual (a90f543), closes #​1266

v10.0.3

Compare Source

Bug Fixes

• filtering by regex (#​1089) (88fbdc2)

v10.0.2

Compare Source

Bug Fixes

• #​1041: apply filteringPath from nockBack before option (6d5bca2), closes #​1041

v10.0.1

Compare Source

Bug Fixes

• package: update debug to version 4.1.0 (0c807c9), closes #​1214

v10.0.0

Compare Source

BREAKING CHANGES

• drop official support for Node < 6

There is no intentional change that breaks usage in Node 4, but as we
stop testing in this no longer supported Node version we recommend to
no update nock if you still rely on Node 4.

The reason why we decided to go ahead and make a breaking version
release is that it became increasingly harder to update dependencies
to the latest versions as they also drop support for Node 4.

Bug Fixes

• #​1203: handle statusCode without payload (21c255f), closes #​1203

Code Refactoring

• update Buffer constructors to from and alloc (c94b89d)

Continuous Integration

• travis: stop testing in Node 4 (139b632)

---

Renovate configuration

📅 Schedule: "after 9am and before 3pm" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".

🔕 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 Renovate Bot. View repository job log here.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

[codecov-io]

Codecov Report

Merging #250 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #250   +/-   ##
=======================================
  Coverage   94.57%   94.57%           
=======================================
  Files         101      101           
  Lines        7242     7242           
  Branches      681      681           
=======================================
  Hits         6849     6849           
  Misses        393      393

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 93d0436...336e09e. Read the comment docs.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

[mayurkale22]

Part of #225