Update minitest requirement from 5.15.0 to 5.23.0

[dependabot]

Updates the requirements on minitest to permit the latest version.

Changelog

Sourced from minitest's changelog.

=== 5.23.0 / 2024-05-15

• 3 minor enhancements:

  • Added -Werror to raise on any warning output. (byroot)
  • Added UnexpectedWarning as a failure summary type, added count to output if activated.
  • Added minitest/manual_plugins.rb w/ new Minitest.load method. (tenderlove)

• 2 bug fixes:

  • Allow empty_run! and reporter to display summary for empty runs. (zzak)
  • Make test task verbose using either rake's -v or -t (was just -t).

=== 5.22.3 / 2024-03-13

• 1 minor enhancement:

  • MASSIVE improvement of minitest's pride plugin output: Frequencies doubled! Sine waves shifted!! Comments improved!!! Colors rotated!!!! (havenwood)

• 3 bug fixes:

  • Improved wording on Minitest::Test#parallelize_me! to clarify it goes INSIDE your test class/describe.
  • Minor changes to tests to pass when tests ran with extra flags (eg -p).
  • Support Ruby 3.4's new error message format. (mame)

=== 5.22.2 / 2024-02-07

• 1 bug fix:

  • Third time's a charm? Remember: 'ensure' is almost always the wrong way to go (for results... it's great for cleaning up).

=== 5.22.1 / 2024-02-06

• 1 bug fix:

  • Don't exit non-zero if no tests ran and no filter (aka, the test file is empty). (I'm starting to think the exit 1 thing for @​tenderlove was a mistake...)

=== 5.22.0 / 2024-02-05

• 1 minor enhancement:

  • Added "did you mean" output if your --name filter matches nothing. (tenderlove)

• 2 bug fixes:

  • Big cleanup of test filtering. Much prettier / more functional.
  • Fix situation where Assertion#location can't find the location. (pftg)

... (truncated)

Commits

• b04feec Branching minitest to version 5.23.0
• f0f17b9 + Added -Werror to raise on any warning output. (byroot)
• 609f1ad Added testW0 rake task.
• d6f62b9 Fixed specs task for pattern_match expectation mapping.
• 56f5068 OMG... Rake.verbose returns Object.new if unset. Fixed by ruby/rake#567, but ...
• 3f14f2a Updated versions/EOL for ruby/rails in readme
• b2a4b43 + Added minitest/manual_plugins.rb w/ new Minitest.load method. (tenderlove)
• 6a8f348 - Make test task verbose using either rake's -v or -t (was just -t).
• 9594e87 - Allow empty_run! and reporter to display summary for empty runs. (zzak)
• ea9caaf Ignore unused block. (ko1)
• 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!

[dependabot]

Superseded by #7044.