Bump minitest from 5.15.0 to 5.22.3

[dependabot[bot]]

Bumps minitest from 5.15.0 to 5.22.3.

Changelog

Sourced from minitest's changelog.

=== 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)

=== 5.21.2 / 2024-01-17

• 1 bug fix:

  • Fixed bug in Minitest::Compress#compress formatting w/ nested patterns. Now recurses properly.

=== 5.21.1 / 2024-01-11

• 1 bug fix:

  • Rails' default backtrace filter can't currently work with caller_locations, so reverting back to caller.

=== 5.21.0 / 2024-01-11

... (truncated)

Commits

• d0a993f Branching minitest to version 5.22.3
• 112cdff - Minor changes to tests to pass when tests ran with extra flags (eg -p).
• 9d2fc6c + MASSIVE improvement of minitest's pride plugin output: Frequencies doubled!...
• 1ead76c - Improved wording on Minitest::Test#parallelize_me! to clarify it goes INSID...
• 93597e5 - Support Ruby 3.4's new error message format. (mame)
• d00cc0d prepped for release
• 6cf8dce - Third time's a charm? Remember: 'ensure' is almost always the wrong way to go.
• 319036f prepped for release
• f92f48d - Don't exit non-zero if no tests ran and no filter (aka, the test file is em...
• 6138c39 prepped for release
• 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 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)

[TomNaessens]

@dependabot close