Print logging information when upgrade failure detected

We are seeing failures in the log that appear like this:

• journalctl --after-cursor s=3fe1fe422f3f482191a361280eed2fdd;i=3b5;b=d8d8e27b9e244b3a83c385fe9dee1358;m=5be7e37;t=617e797638e8f;x=967810e36b39afc --unit apertis-update-manager
• grep -qE Ostree upgrade failed
• echo update failed update failed
• RESULT=1
• break

It suggests that the board's journal may contain some information about the failure, but we currently aren't seeing this in the LAVA logs.

On failure print out the logs that are being used to determine the failure to see if we can understand the issue better.

Signed-off-by: Martyn Welch martyn.welch@collabora.com