Without this change the tree of jobs shows "health" with a series of 7
"run" jobs nested underneath.
Add the check name from the input to the job name.

Moving over from https://github.com/mosuem/merger/.

We might want to move the issue transfer tool from `repo_manage` to this
tool as well, it would be cleaner.

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>

---------

Co-authored-by: Devon Carew <devoncarew@google.com>

Optionally transfer issues as well when running trebuchet.

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>

- contribute a prompt benchmarking script

This contributes a contribute a prompt benchmarking script; it gets
label information for ~100 existing issues - assumed to be correctly
labelled - and compares them against the labels predicted by the prompt.
This will allow us to benchmark prompt changes to know whether we're
improving things or not. Note that there are no prompt improvements in
this PR (just some updates for area label changes).

The benchmarking can be re-run via `dart tool/bench.dart`.

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>

fix calculation for the labels to apply

Bumps the github-actions group with 3 updates: [peter-evans/find-comment](https://github.com/peter-evans/find-comment), [actions/upload-artifact](https://github.com/actions/upload-artifact) and [peter-evans/create-or-update-comment](https://github.com/peter-evans/create-or-update-comment).

Updates `peter-evans/find-comment` from d24cbe12e65c22d4761a4d5082ca0bb42bc5aaea to d0ee7939ee99ba35820c3e58de972e57ff8bb890
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/peter-evans/find-comment/commit/d0ee7939ee99ba35820c3e58de972e57ff8bb890"><code>d0ee793</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.45 to 18.19.47 (<a href="https://redirect.github.com/peter-evans/find-comment/issues/318">#318</a>)</li>
<li><a href="https://github.com/peter-evans/find-comment/commit/0d01c40de219b33a133ca469703736c60227734f"><code>0d01c40</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.44 to 18.19.45 (<a href="https://redirect.github.com/peter-evans/find-comment/issues/317">#317</a>)</li>
<li><a href="https://github.com/peter-evans/find-comment/commit/d128bde458bafdcbba853adbe44576fb0c644d09"><code>d128bde</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.43 to 18.19.44 (<a href="https://redirect.github.com/peter-evans/find-comment/issues/316">#316</a>)</li>
<li><a href="https://github.com/peter-evans/find-comment/commit/ffa20ece46999b47ee26adc0e2d219cab5794367"><code>ffa20ec</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.42 to 18.19.43 (<a href="https://redirect.github.com/peter-evans/find-comment/issues/315">#315</a>)</li>
<li>See full diff in <a href="https://github.com/peter-evans/find-comment/compare/d24cbe12e65c22d4761a4d5082ca0bb42bc5aaea...d0ee7939ee99ba35820c3e58de972e57ff8bb890">compare view</a></li>
</ul>
</details>
<br />

Updates `actions/upload-artifact` from 4.3.4 to 4.4.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/actions/upload-artifact/releases">actions/upload-artifact's releases</a>.</em></p>
<blockquote>
<h2>v4.4.0</h2>
<h2>Notice: Breaking Changes ⚠️</h2>
<p>We will no longer include hidden files and folders by default in the <code>upload-artifact</code> action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, <code>include-hidden-files</code>, to continue to do so.</p>
<p>See <a href="https://github.blog/changelog/2024-08-19-notice-of-upcoming-deprecations-and-breaking-changes-in-github-actions-runners/">&quot;Notice of upcoming deprecations and breaking changes in GitHub Actions runners&quot;</a> changelog and <a href="https://redirect.github.com/actions/upload-artifact/issues/602">this issue</a> for more details.</p>
<h2>What's Changed</h2>
<ul>
<li>Exclude hidden files by default by <a href="https://github.com/joshmgross"><code>@�joshmgross</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/598">actions/upload-artifact#598</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4.3.6...v4.4.0">https://github.com/actions/upload-artifact/compare/v4.3.6...v4.4.0</a></p>
<h2>v4.3.6</h2>
<h2>What's Changed</h2>
<ul>
<li>Revert to <code>@�actions/artifact</code> 2.1.8 by <a href="https://github.com/robherley"><code>@�robherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/594">actions/upload-artifact#594</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4...v4.3.6">https://github.com/actions/upload-artifact/compare/v4...v4.3.6</a></p>
<h2>v4.3.5</h2>
<h2>What's Changed</h2>
<ul>
<li>Bump <code>@�actions/artifact</code> to v2.1.9 by <a href="https://github.com/robherley"><code>@�robherley</code></a> in <a href="https://redirect.github.com/actions/upload-artifact/pull/588">actions/upload-artifact#588</a>
<ul>
<li>Fixed artifact upload chunk timeout logic <a href="https://redirect.github.com/actions/toolkit/pull/1774">#1774</a></li>
<li>Use lazy stream to prevent issues with open file limits <a href="https://redirect.github.com/actions/toolkit/pull/1771">#1771</a></li>
</ul>
</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/upload-artifact/compare/v4.3.4...v4.3.5">https://github.com/actions/upload-artifact/compare/v4.3.4...v4.3.5</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/actions/upload-artifact/commit/50769540e7f4bd5e21e526ee35c689e35e0d6874"><code>5076954</code></a> Merge pull request <a href="https://redirect.github.com/actions/upload-artifact/issues/598">#598</a> from actions/joshmgross/exclude-hidden-files</li>
<li><a href="https://github.com/actions/upload-artifact/commit/d52396ac5d312b1bda1b9fe2ae55d862c65abd68"><code>d52396a</code></a> Add a warning about enabling <code>include-hidden-files</code></li>
<li><a href="https://github.com/actions/upload-artifact/commit/710f36207581d49e465ccbed3e007c317290fe11"><code>710f362</code></a> Remove &quot;merged&quot; from <code>include-hidden-files</code> input description</li>
<li><a href="https://github.com/actions/upload-artifact/commit/3b315f26f6f828f74089e1863e67e60e48e37563"><code>3b315f2</code></a> <code>npm run release</code> again �</li>
<li><a href="https://github.com/actions/upload-artifact/commit/3be2180eb79b56341b1b127ca06a5adba2a5a3e4"><code>3be2180</code></a> Remove another trailing comma</li>
<li><a href="https://github.com/actions/upload-artifact/commit/453e8d0a40444939146df5febed0b1221b9dd073"><code>453e8d0</code></a> Update glob license</li>
<li><a href="https://github.com/actions/upload-artifact/commit/0a398c14804ead69f18a166f0a99f91239261ee5"><code>0a398c1</code></a> <code>npm run release</code></li>
<li><a href="https://github.com/actions/upload-artifact/commit/a0c40cf60283f329afac2bc0fa77f1a59fa11e6e"><code>a0c40cf</code></a> Update to latest <code>@actions/glob</code> and fix tests</li>
<li><a href="https://github.com/actions/upload-artifact/commit/acb59e47763b6e601a344d04cf3c082ee336b709"><code>acb59e4</code></a> <code>lint</code></li>
<li><a href="https://github.com/actions/upload-artifact/commit/cb6558bb10fe4afe4054d0be4b3136e673eb5e7f"><code>cb6558b</code></a> Exclude hidden files by default</li>
<li>Additional commits viewable in <a href="https://github.com/actions/upload-artifact/compare/0b2256b8c012f0828dc542b3febcab082c67f72b...50769540e7f4bd5e21e526ee35c689e35e0d6874">compare view</a></li>
</ul>
</details>
<br />

Updates `peter-evans/create-or-update-comment` from e5db2e44ee874e3b99b0e4137f1c0685435102e7 to b91ff48c6f29dc258316a8b76d3dd6b8c6ffff1c
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/peter-evans/create-or-update-comment/commit/b91ff48c6f29dc258316a8b76d3dd6b8c6ffff1c"><code>b91ff48</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.45 to 18.19.47 (<a href="https://redirect.github.com/peter-evans/create-or-update-comment/issues/349">#349</a>)</li>
<li><a href="https://github.com/peter-evans/create-or-update-comment/commit/2830915767dd95c84b29b83d41562b01c53be401"><code>2830915</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.44 to 18.19.45 (<a href="https://redirect.github.com/peter-evans/create-or-update-comment/issues/348">#348</a>)</li>
<li><a href="https://github.com/peter-evans/create-or-update-comment/commit/0c2659f0c1989e0e05adddb01d9e680fccae80fc"><code>0c2659f</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.43 to 18.19.44 (<a href="https://redirect.github.com/peter-evans/create-or-update-comment/issues/347">#347</a>)</li>
<li><a href="https://github.com/peter-evans/create-or-update-comment/commit/842a986c495c2be92af382b61e07ab71e1448c4c"><code>842a986</code></a> build(deps-dev): bump <code>@�types/node</code> from 18.19.42 to 18.19.43 (<a href="https://redirect.github.com/peter-evans/create-or-update-comment/issues/345">#345</a>)</li>
<li>See full diff in <a href="https://github.com/peter-evans/create-or-update-comment/compare/e5db2e44ee874e3b99b0e4137f1c0685435102e7...b91ff48c6f29dc258316a8b76d3dd6b8c6ffff1c">compare view</a></li>
</ul>
</details>
<br />

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`.

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions

</details>

To fix CI errors such as in #293 

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>

So that the transferred issues before the failure happened are not
unlabeled.

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>

- update the prompt to include triaging issues w/ `needs-info` labels
- `[breaking change]` issues should have `breaking-change-request`
labels but don't necessarily need area labels
- add 5 'few-shot' examples in the classification prompt
- update benchmark expectations
- classification performance has generally improved from 56% to 65%

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>