Update chefstyle requirement from 1.7.2 to 1.7.4

[dependabot]

Updates the requirements on chefstyle to permit the latest version.

Changelog

Sourced from chefstyle's changelog.

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)

v1.7.1 (2021-02-15)

Merged Pull Requests

• Add new Chef/Ruby/GemspecLicense cop #127 (tas50)
• Update to RuboCop 1.10 #128 (tas50)

v1.6.2 (2021-02-01)

Merged Pull Requests

• Update RuboCop to 1.9.1 #126 (tas50)

v1.6.1 (2021-01-28)

Merged Pull Requests

• Update RuboCop to 1.8.1 #122 (tas50)
• Add a cop for detecting legacy powershell methods #123 (tas50)
• Update to RuboCop 1.9 #125 (tas50)

v1.5.9 (2020-12-30)

Merged Pull Requests

• Update to RuboCop 1.7 #121 (tas50)

v1.5.8 (2020-12-21)

Merged Pull Requests

• Update to RuboCop 1.6.1 #119 (tas50)

v1.5.7 (2020-12-04)

Merged Pull Requests

• Update to RuboCop 1.5.2 #118 (tas50)

v1.5.6 (2020-12-01)

Merged Pull Requests

• Update to Rubocop 1.4.1 #114 (tas50)
• Allow 1 line defs w/o a space between #115 (tas50)

... (truncated)

Commits

• a612150 Bump version to 1.7.4 by Chef Expeditor
• 542c763 Merge pull request #132 from chef/bump_rubocop
• c398ed1 Update Rubocop to 1.12
• 797f464 Vendor rubocop-1.12.0 upstream configuration.
• 6ce904f Bump version to 1.7.3 by Chef Expeditor
• f7ba0d3 Merge pull request #130 from chef/ruby_3
• 5a3d622 Add Ruby 3.0 testing
• 8a1ad4a Update CHANGELOG.md to reflect the promotion of 1.7.2
• 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

[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!