Improve handling of fatal CLI errors

[henrymercer]

Currently we are losing information about CLI errors in database {finalize,interpret-results,run-queries}. When the CLI command includes "A fatal error occurred" in its stderr, we lose other context about the error (such as whether it was an OOM, or out of disk, or something else) in the Actions run summary and in telemetry.

Furthermore, the Action is suppressing the improved errors for no code found shipped in CodeQL v2.12.4.

This PR stops suppressing these errors by displaying fatal errors in full, and using the CLI error message for database finalize no code found errors for CodeQL CLI v2.12.4 and later. Most of the commits are tweaking the error message to try to improve its utility. In particular, we're quite keen to get it on a single line if we can, as this lets us include all the useful detail we can on the Actions run summary page.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.