issue-labeler: A version upgrade is needed

Nobody has claimed this yet.

GitHub is deprecating NodeJS 20 actions over the summer period, which will make the `issue-labeler` not work anymore. See for example most recent runs in the LLVM repo: https://github.com/llvm/llvm-project/actions/runs/25725231818

> **automate-issues-labels**
> Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: **llvm/actions/issue-labeler@89a8cf80982d830faab019237860b344a6390c30**. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true` environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true`. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Start by locating the issue-labeler action and its workflow or action metadata, then inspect the versions available for Node.js 24 support. Use the relevant GitHub Actions run to verify the current deprecation warning. Done means the action runs successfully without the Node.js 20 deprecation warning.

Written by the indexing model from the issue text.