build(deps): bump mikepenz/action-junit-report from 4 to 5

[dependabot]

Bumps mikepenz/action-junit-report from 4 to 5.

Release notes

Sourced from mikepenz/action-junit-report's releases.

v5

• no changes

v5.0.0

[!NOTE]
v5 adjusts the format of the summary output. If you depend on the prior format, please verify the simplified format works for your usecase.

🚀 Features

• Introduce new ability to include flaky tests in summary
  • PR: #1115
• Include flakyFailures block in retry count
  • PR: #1118
• Refactor testParser to enable it for future usecases
  • PR: #1119
• Allow configuration of bread_crumb_delimiter
  • PR: #1120
• Introduce flag to comment summary on PR
  • PR: #1167
• Improve transformer performance
  • PR: #1182
• Provide optimised class detection skipping globber if not required
  • PR: #1183
• Upgrade dependencies to latest major version
  • PR: #1220
• Add new API to skip annotations all-to-gether
  • PR: #1221
• Introduce flag to fail_on_parse_error
  • PR: #1222
• Improve parsing logic for nested suites
  • PR: #1224
• Configuration to enable grouping by TestSuite in the Detail Summary
  • PR: #1225

🐛 Fixes

• Require pull_request trigger to attach comment
  • PR: #1181

💬 Other

• Move test CI steps
  • PR: #1116
• Slight code cleanup
  • PR: #1223

📦 Dependencies

• Upgrade dependencies
  • PR: #1117

... (truncated)

Commits

• a427a90 - ignorePreReleases for changelog
• 6141c38 Merge pull request #1231 from gilesw/docs/example-stanza-for-forked-non-forke...
• eb88208 - slightly rephrase updated README
• 511b061 Merge pull request #1237 from mikepenz/feature/dependency_updates_20241116
• 3caf5b3 - upgrade npm dependencies
• 46ad281 docs: try to fix yaml rendering
• 56596cc docs: small example to show a use case for annotate_only
• 1c2f98d - update README for v5 action
• ec3a351 Merge pull request #1225 from mikepenz/feature/grouped_summary
• b317015 - html formatting
• 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)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign anjannath for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a crc-org member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.