Meta: Parse stdout/stderr from failed build commands to search for common pitfalls

[ADKaster]

We have an entire section in our docs that talks about how to avoid getting tricked by the red herring messages emitted by vcpkg in manifest mode when run via CMake:

https://github.com/LadybirdBrowser/ladybird/blob/master/Documentation/BuildInstructionsLadybird.md#unable-to-find-a-build-program-corresponding-to-ninja

Now that we've got ladybird.sh rewritten to ladybird.py, it should be easier to wrangle a developer assist to tee the standard streams somewhere for analysis post-execution of CMake. This post-processing could check if the command worked, and if it failed, parse the stdout/stderr looking for that Ninja message and any vcpkg error messages to highlight them to the developer/user in a clearer way.

This solution needs to not simply swallow all stdout/sterr from CMake though, as that would result in the terminal being completely idle for the entirely of the vpckg build. On even very good recent machines, this can be a 30 minute to 1h affair. The terminal looking idle for that long is likely to be more confusing than a misleading error message from CMake.

When implementing this, we should check whether the vpckg error log messages actually are clickable from modern terminal emulators. If not, we should wrap them in OSC-8 tags.