Description:
When there's a Severity: high failure from npm audit --audit-level=high, the workflow fails

Task version:
main

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:

1. Sync a fork of this repository after the release of a new Severity: high item but before the corresponding PR is merged to this repository

Expected behavior:
A useful error on the overview explaining what's gone wrong (the severity high entries)

Actual behavior:

Annotations

9 errors
❌ Basic validation / build (macos-latest)
Process completed with exit code 1.
❌ Basic validation / build (macos-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (macos-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (ubuntu-latest)
Process completed with exit code 1.
❌ Basic validation / build (ubuntu-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (ubuntu-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (windows-latest)
Process completed with exit code 1.
❌ Basic validation / build (windows-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (windows-latest)
Java setup process failed due to: Available version not found

To a naive reader, it feels like the problem is "Java setup process failed due to: Available version not found", but that doesn't appear to be the problem at all. Note that this is error also lousy, but it's out of scope.