Update chefstyle requirement from 1.1.1 to 1.1.2

[dependabot-preview]

Updates the requirements on chefstyle to permit the latest version.

Changelog

Sourced from chefstyle's changelog.

v1.1.2 (2020-06-25)

Merged Pull Requests

• Update Rubocop to 0.86 #91 (tas50)

v1.1.1 (2020-06-08)

Merged Pull Requests

• Require RuboCop 0.85.1 #90 (tas50)

v1.1.0 (2020-06-02)

Merged Pull Requests

• Update RuboCop engine from 0.83 to 0.85 #89 (tas50)

v1.0.5 (2020-05-12)

Merged Pull Requests

• Add back the Gemspec, but remove gemfile dev groups #85 (tas50)
• Make sure our comments line up with our code #86 (tas50)
• Update RuboCop to 0.83 #87 (tas50)

v1.0.2 (2020-04-20)

Merged Pull Requests

• Stop shipping the Gemfile and Gemspec in the gem #84 (tas50)

v1.0.1 (2020-04-16)

Merged Pull Requests

• Update to Rubocop 0.81.0 #82 (tas50)
• Update to RuboCop 0.82 engine #83 (tas50)

v0.15.1 (2020-03-25)

Merged Pull Requests

• enable Lint/UriEscapeUnescape #78 (lamont-granquist)
• Update the RuboCop engine to 0.80.1 #79 (tas50)
• Update buildkite testing #80 (tas50)
• Allow chefstyle to autocorrect indentation issues #81 (tas50)

v0.14.1 (2020-02-12)

Merged Pull Requests

• Use require_relative instead of require #77 (tas50)

v0.14 (2019-11-08)

Merged Pull Requests

Commits

• ed16277 Bump version to 1.1.2 by Chef Expeditor
• 77d8e03 Merge pull request #91 from chef/0.86
• 1bf709c Update RuboCop to 0.86
• 309b638 Update CHANGELOG.md to reflect the promotion of 1.1.1
• 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 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 the .dependabot/config.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[chef-expeditor]

Hello dependabot-preview[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!

[james-stocks]

Thanks robot