tools: add resume-ci label handling

[panva]

Adds [resume-ci] label handling alongside [request-ci]. The scheduled workflow selects up to five approved PRs with either label in one query. A shared script checks each PR's current labels and chooses ncu-ci run or ncu-ci resume, skipping PRs with neither label.

Failed resume attempts receive [resume-ci-failed] and a comment with a diagnostic summary, full output, and workflow link.

If both request labels are present, the script removes them, adds [request-ci-failed] and [resume-ci-failed], and reports the conflict once without starting or resuming CI.

Before merging:

• Merge nodejs/node-core-utils PR adding ncu-ci resume.
• Publish an @node-core/utils release containing that change.
• Create the [resume-ci] label in nodejs/node.
• Create the [resume-ci-failed] label in nodejs/node.

[nodejs-github-bot]

Review requested:

• @nodejs/actions
• @nodejs/tsc

[jasnell]

I haven't yet looked into the details but a question: I assume that resume-ci will fail if new commits have been added since the last run?

[panva]

I haven't yet looked into the details but a question: I assume that resume-ci will fail if new commits have been added since the last run?

yes.

[aduh95]

I haven't yet looked into the details but a question: I assume that resume-ci will fail if new commits have been added since the last run?

No it won't be picked up until it's approved

[panva]

Well, if an approval for the latest commit is there and [resume-ci] is still present then it will fail to start and report such.

[mcollina]

lgtm

[panva]

@jasnell @mcollina thank you for the reviews, nodejs/node-core-utils#1187 needs those ✅s too before being able to proceed here.