feat(release): gate on every named workflow, not just one

[trakhimenok]

require_workflow_success took a single workflow name, so a repository with more than one quality workflow could gate only one of them. The rest were free to be red while the release proceeded. That is the same hole the input was added to close, just narrower.

The change

Accept a comma-separated list and require every named workflow to be green:

require_workflow_success: 'Go CI, Integration tests'

A single name behaves exactly as before, so no consumer needs to change.

The guard checks all of them and reports every one that is not green rather than stopping at the first, so one run shows the whole picture instead of hiding the second failure behind the first. The timeout applies per named workflow, which the input description now says.

Situation	Result
Every named workflow green or skipped	release proceeds
Any one not green	refused, and the error names each one that was not
A name matching no workflow	refused, listing what does exist
A named workflow with no run for the commit	skipped as not applicable, with a notice

Verification

• Tests cover all-green and one-red-among-several, asserting the failure names the red workflow and still reports the green one. Confirmed to fail when the script is sabotaged to gate only the first name, so they cannot pass against the old behaviour.
• The script embedded in the YAML is byte-identical to one exercised against live GitHub data across three cases: single name green, two names both green, and two names with one red. The mixed case correctly refused while reporting the green one.
• Full suite green.

🤖 Generated with Claude Code