Update net-ssh requirement from >= 2.9, < 7.0 to >= 2.9, < 8.0

[dependabot[bot]]

Updates the requirements on net-ssh to permit the latest version.

Changelog

Sourced from net-ssh's changelog.

=== 6.1.0

• Adapt to ssh's default behaviors when no username is provided. When Net::SSH.start user is nil and config has no entry we default to Etc.getpwuid.name() instead of Etc.getlogin(). #749

=== 6.1.0.rc1

• Make sha2-{256,512}[email protected] MAC default again #761
• Support algorithm subtraction syntax from ssh_config #751

=== 6.0.2

• Fix corrupted hmac issue in etm hmac #759

=== 6.0.1

• Make sha2-{256,512}[email protected] MAC opt-in as they seems to have issues #757

=== 6.0.0

• Support empty lines and comments in known_hosts [donoghuc, #742]
• Add sha2-{256,512}[email protected] MAC algorithms [graaff, #714]

=== 6.0.0 beta2

• Support :certkeys and CertificateFile configuration option [Anders Carling, #722]

=== 6.0.0 beta1

• curve25519sha256 support [Florian Wininger ,#690]
• disabled insecure algs [Florian Wininger , #709]

=== 5.2.0

=== 5.2.0.rc3

• Fix check_host_ip read from config
• Support ssh-ed25519 in known hosts

=== 5.2.0.rc2

• Read check_host_ip from ssh config files

=== 5.2.0.rc1

• Interpret * and ? in know_hosts file [Romain Tartière, #660]
• New :check_host_ip so ip checking can be disabled in known hosts [Romain Tartière, #656]

=== 5.1.0

... (truncated)

Commits

• 74919ef 6.1 release prepare
• 3768f1f Merge pull request #762 from noda50/master
• 07a4c1d Let use Etc.getpwuid.name() instead of Etc.getlogin to adapt default behavior...
• 139126b 6.1.0.rc1
• 9266909 Merge pull request #761 from net-ssh/revert-757-opt-in-etm-hmac
• ccb874c Revert "Make hmac-sha2-{256,512}-etm opt-in"
• a6db052 Merge pull request #756 from keithrbennett/clarify-readme
• 996b6c8 Merge pull request #760 from net-ssh/fwininger-patch-1
• 39d70af Merge pull request #759 from mfazekas/fix-corrup-hmac-issue
• 0294c53 Update README.md
• 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!