Update chefstyle requirement from 2.0.7 to 2.0.8

[dependabot]

Updates the requirements on chefstyle to permit the latest version.

Changelog

Sourced from chefstyle's changelog.

v2.0.8 (2021-08-12)

Merged Pull Requests

• Update RuboCop to 1.19 #145 (tas50)

v2.0.7 (2021-07-24)

Merged Pull Requests

• Update RuboCop to 1.18.4 #144 (tas50)

v2.0.6 (2021-07-06)

Merged Pull Requests

• Update RuboCop engine to 1.18.3 #142 (tas50)

v2.0.5 (2021-06-24)

Merged Pull Requests

• Update RuboCop 1.15 -> 1.17 #140 (tas50)

v2.0.4 (2021-05-27)

Merged Pull Requests

• Update RuboCop engine to 1.15 #138 (tas50)

v2.0.3 (2021-05-05)

Merged Pull Requests

• Update to RuboCop 1.13 and remove Ruby 2.4 support #134 (tas50)
• Upgrade to GitHub-native Dependabot #135 (dependabot-preview[bot])
• Update RuboCop to 1.14 #136 (tas50)
• Make sure the gem requires Ruby 2.5+ #137 (tas50)

v1.7.5 (2021-04-17)

Merged Pull Requests

• Update to RuboCop 1.12.1 #133 (tas50)

v1.7.4 (2021-03-24)

Merged Pull Requests

• Add Ruby 3.0 testing #130 (tas50)
• Update RuboCop to 1.12 #132 (tas50)

v1.7.2 (2021-03-09)

Merged Pull Requests

• Vendor rubocop-1.11.0 upstream configuration. #129 (tas50)

... (truncated)

Commits

• 63277d9 Bump version to 2.0.8 by Chef Expeditor
• 6b4fdf4 Merge pull request #145 from chef/bump_rubocop_19
• b6308aa Update to RuboCop 1.19
• 92b9868 Vendor rubocop-1.19.0 upstream configuration.
• 47dcaf9 Update CHANGELOG.md to reflect the promotion of 2.0.7
• See full diff 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]

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!