Update rspec-its requirement from ~> 1.2 to >= 1.2, < 3.0

[dependabot]

Updates the requirements on rspec-its to permit the latest version.

Changelog

Sourced from rspec-its's changelog.

1.3.1 / 2024-10-23

full changelog

Bug fixes:

• Prevent overridden example methods causing issues by creating our own Example Group creation alias __its_example. (Jon Rowe, #95)

1.3.0 / 2019-04-09

full changelog

Enhancements:

• Introduced will and will_not as to allow one line block expectations. (Russ Buchanan, #67)

1.2.0 / 2015-02-06

full changelog

Breaking Changes:

Enhancements:

• Introduced are_expected as alias for is_expected

Bug fixes:

• Restored ability to pass key/value metadata parameters, broken by rspec/rspec-its@71307bc

1.1.0 / 2014-04-13

full changelog

Breaking Changes:

Enhancements:

• For hashes, multiple array elements are treated as successive access keys
• Metadata arguments are now supported

Bug fixes:

• Enable its example selection by line number in command line

1.0.1 / 2014-04-13

full changelog

Bug fixes:

• Maintain implicit subject in all cases (addresses problem with latest RSpec 3 version)

1.0.0 / 2014-02-07

full changelog

Breaking Changes:

... (truncated)

Commits

• 6dec295 v1.3.1
• f3727a3 Changelog for #95
• 096736d Merge pull request #95 from rspec/fix-example-usage
• 0fd24f5 Move JRUby 9.1.17 to legacy setup
• d25c18f Modernise legacy ruby setup
• 0020fd3 allow insecure node version on legacy ci
• 4c5ce67 Fix rspec-metagem
• 1c245c4 Remove deprecated raise_error
• 692db5f Fix usage of example for when its redefined
• 14297a7 Merge pull request #89 from rspec/dependabot/github_actions/actions/checkout-3
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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!

[Nik08]

Omnibus adhoc is successful https://buildkite.com/chef/inspec-inspec-inspec-5-omnibus-adhoc/builds/107