Bump nock from 10.0.6 to 11.3.3

[dependabot-preview]

Bumps nock from 10.0.6 to 11.3.3.

Release notes

Sourced from nock's releases.

v11.3.3

11.3.3 (2019-09-05)

Bug Fixes

• types: DataMatcher to allow valid JSON scalars. (#1703) (a700fa2), closes #1702

v11

Upgrading from Nock 10 to Nock 11

Bug fixes and internal improvements

Nock 11 includes many under-the-hood improvements, including a fully offline
test suite and 100% test coverage. The codebase was also converted to ES6
syntax and formatted with Prettier. Leaning on the test coverage, some
substantial refactors have begun.

Many bug fixes are included. See the detailed changelog below or the
[compare view][compare] for details.

Fabulous new features for developers

1. The library ships with TypeScript definitions. (Added in v11.3)
2. Add support for the http.request signatures added in Node 10.9
3. Scopes can be filtered using the system environment or any external factor
   using e.g. .conditionally(() => true)
4. In-flight modifications to headers are preserved in mock requests.
5. Recorded mocks can be stringified using custom code in the afterRecord()
   post-processing hook. When afterRecord() returns a string, the
   recorder will no longer attempt to re-stringify it. (Added in v11.3)
6. Reply functions passed to .reply() can now be async/promise-returning.
7. Specifying reply headers, either via .reply() or .defaultReplyHeaders(),
   can now be done consistently using an object, Map, or flat array.

Breaking changes

For many developers no code changes will be needed. However, there are several
minor changes to the API, and it's possible that you will need to update your
code for Nock to keep working properly. It's unlikely that your tests will
falsely pass; what's more probable is that your tests will fail until the
necessary changes are made.

1. Nock 11 requires Node 8 or later. Nock supports and tests all the "current"
   and "maintenance" versions of Node. As of now, that's Node 8, 10, and 12.

2. In Nock 10, when reply() was invoked with a function, the return values were
   handled ambiguously depending on their types.

   Consider the following example:

... (truncated)

Commits

• a700fa2 fix(types): DataMatcher to allow valid JSON scalars. (#1703)
• 9d5cda0 docs(README): adapt badges for @​latest release
• cfc129c chore(deps): bump eslint-utils from 1.4.0 to 1.4.2 (#1698)
• 21733b4 refactor: Remove the last of the real hostnames (#1691)
• f00f0f3 test: Replace test_s3 with test of Expect: 100-continue (#1690)
• b83e720 fix(types): use export = and declares (#1695)
• 66799f3 refactor: Refactor net connect tests (#1688)
• dafa35b docs: Add "Common issues" section documenting got automatic retrying (#1687)
• 11a9517 style: Minor style improvements (#1693)
• 50c821b test: Add todo test for conflict between hostnames (#1109)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[coveralls]

Pull Request Test Coverage Report for Build 210

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 98.024%

---

Totals
Change from base Build 132:	0.0%
Covered Lines:	145
Relevant Lines:	147

---

💛 - Coveralls

[dependabot-preview]

Superseded by #83.