Bump korthout/backport-action from 4.3.0 to 4.5.0

[dependabot]

Bumps korthout/backport-action from 4.3.0 to 4.5.0.

Release notes

Sourced from korthout/backport-action's releases.

Backport-action v4.5.0

What's Changed

This release introduces a new comment_style input with two options:

• legacy (default): one comment per target branch. This is the same behavior as you know from previous versions.
• summary: a single comment per workflow run that updates progressively as each target is processed. It links back to the workflow run, shows a status table for every target, and includes recovery hints for known failure modes (e.g. push permission denied, cherry-pick conflicts).

Here's what a summary comment looks like mid-run:

Backport-action is backporting this pull request in workflow run 15439584062.

Target	Status
stable/8.7	✅ Created #612
stable/8.6	⚠️ Drafted with conflicts #613
stable/8.5	❌ Failed
stable/8.4	➖ Skipped (PR already exists)
stable/8.3	⌛ Pending

Tried to cherry-pick commits onto stable/8.5, but the cherry-pick failed.

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin stable/8.5
git worktree add -d .worktree/stable/8.5 origin/stable/8.5
cd .worktree/stable/8.5
git switch --create <backport-branch-name>
git cherry-pick -x a1b2c3d e4f5g6h

Opt in by adding comment_style: summary to your workflow:

- uses: korthout/backport-action@v4.5.0
  with:
    comment_style: summary

I'd love feedback on summary while it's opt-in. Drop a comment on #611 with anything that's confusing, missing, or broken. Once it's proven stable in real workflows, I plan to make it the default and deprecate legacy in a future major release.

• Add summary comment style by @​korthout in korthout/backport-action#611

Updated dependencies

• Update korthout/backport-action action to v4.4.0 by @​renovate[bot] in korthout/backport-action#606
• Update dependency @​actions/github to v9.1.1 by @​renovate[bot] in korthout/backport-action#614

... (truncated)

Commits

• 7c3f6cd dist: release 4.5.0
• 87a29c6 dist: build new artifacts
• 0ee69ba Merge pull request #611 from korthout/korthout-415-summary-comment-2
• 1db2c6e test: assert summary updates target the created comment id
• 716c6c8 test: tighten progressive-update assertions to count markers
• a5c7207 test: bind details blocks to targets in multi-failure case
• bb51aed test: tighten and reorganize comment-formatter tests
• e24e1e6 style: fix typos and GitHub branding in comment formatters
• 8beb4f8 fix(summary): distinguish total vs partial failure in intro
• 188e2dc Merge pull request #621 from korthout/renovate/lock-file-maintenance
• 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 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.