mxcli test: print the build error first when a test fails to build; retry once on an mxbuild --serve timeout #1685

What happens

When one test in tests/*.test.mdl does not build (for example mxbuild CE0161 in an XPath), mxcli test --local reports only Passed: 0, Errors: 1, Skipped: n. The build error that caused it is not printed first, so the run looks as if every test failed for no reason.

A transient mxbuild --serve timeout produces the same summary: Error: local runtime: build: serve build request to http://127.0.0.1:6544/build: ... context deadline exceeded. A second run passes without any change.

Expected

1. When the build fails, print the build error (code, document, message) first and prominently, before the summary line.
2. Retry the build once on an mxbuild --serve timeout before reporting an error.

Evidence

A test file with the XPath where Status = Mod.ENUM_X.VALUE and Name like 'A-%' passes mxcli check. mxcli test --local then ends with Passed: 0, Errors: 1, Skipped: 108; the CE0161 is only found by building the project separately. Related: #1396 (hang after tests), #1645.

Environment

mxcli 0.28.0, Studio Pro 11.12.4, Windows 11. Found by the AppGen tooling (Ciphix) on a test app.