Update mocha requirement from ~> 1.1 to ~> 2.0

[dependabot[bot]]

Updates the requirements on mocha to permit the latest version.

Changelog

Sourced from mocha's changelog.

2.0.1

External changes

• Fix LoadError when using v2.0.0 with Ruby < v2.7 by moving declaration of runtime dependency on ruby2_keywords gem from Gemfile to mocha.gemspec - thanks to @​mishina2228 for reporting (#581, #582, cdeb0356)

2.0.0

External changes

• Remove support for Ruby v1.9 - thanks to @​wasabigeek (#552)
• Support strict keyword argument matching - see docs for Expectation#with & Configuration#strict_keyword_argument_matching= - thanks to @​wasabigeek (#446,#535,#544,#562)
• Deprecate Hash args that don't strictly match (#563,981c31be)
• Drop support for older versions of test-unit - gem versions of test-unit earlier than v2.5.1 and versions of test-unit from the Ruby v1.8 standard library are no longer supported (#540,969f4845)
• Drop support for older versions of minitest - versions of minitest earlier than v3.3.0 are no longer supported (#541,ca69dc9e)
• Remove deprecated mocha/setup.rb mechanism (642a0ff4)
• Add missing docs for API#stub parameter (257b4cb4)
• Remove optional reinstatement of v1.9 behaviour (#436,#438,#569,1473ee25)
• Remove deprecated methods in Configuration (#421,e7ff7528)
• Fail fast when mock receives invocations in another test (#440,#442,cb054d59)
• Improve docs re using matchers in Expectation#with (da7237cd)
• Expand Expectation#with docs re keyword arguments (fed6808d)
• Improve docs for strict_keyword_argument_matching (8d8f881d)
• Remove deprecated Rails plugin init.rb file (1c617175)
• Improve strict keyword argument matching deprecation warning by including the source location of the stub definition (77c0d4cc)
• Add README section re semantic versioning (00758246)

Internal changes

• Separate linting from tests in terms of Rake tasks & CircleCI jobs - thanks to @​wasabigeek (#556)
• Remove tests specific to Ruby v1.8 behaviour (46fca7ac, 3b369e99)
• Multi-line rubocop disable in Mock#method_missing (af2194c4)
• Remove unused arg for HashMethods#mocha_inspect (4f59e27f)
• Improve test runner assertions - failure vs error (eec7200a)
• Improve test coverage of PositionalOrKeywordHash (c294fe70)
• More consistent Test::Unit & Minitest integration (27dd3817)
• Remove redundant require statements (d82218a8,fa17b114)
• Add missing require statement (73493761)
• Disable Style/Semicolon cop globally (8cd0b705)

1.16.0

External changes

• Default Configuration#reinstate_undocumented_behaviour_from_v1_9= to false (6fcaf947)
• Deprecate Configuration#reinstate_undocumented_behaviour_from_v1_9= (a797c5fd)

Internal changes

... (truncated)

Commits

• a6d6ac2 Bump version to 2.0.1 & prepare for release
• cdeb035 ruby2_keywords is runtime dep not development dep
• c5cf324 [skip ci] Update documentation for v2.0.0.
• fcd5450 Bump version to 2.0.0 & prepare for release
• 0075824 Add README section re semantic versioning
• 1099679 Improve docs for strict keyword argument matching
• a5e07fc [skip ci] Add v1.16.0 into release docs
• e32e9e5 [skip ci] Update documentation for v2.0.0.alpha.1
• 90e1157 Bump version to 2.0.0.alpha.1 & prepare for release
• 77c0d4c Improve keyword argument deprecation warning
• 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)

[chef-expeditor[bot]]

Hello dependabot[bot]! Thanks for the pull request!

Here is what will happen next:

1. Your PR will be reviewed by the maintainers.
2. Possible Outcomes a. If everything looks good, one of them will approve it, and your PR will be merged. b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner. c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!

[dependabot[bot]]

Superseded by #748.