DevX: Improve error reporting for benchmark jobs.

[guangy10]

🐛 Describe the bug

As shown in an example run, there are two issues that make it difficult to understand the expected behavior and locate the exact error:

1. Unexpected job success status: Two configurations failed to export, yet the benchmark-on-device jobs were still marked as successful (highlighted in the red box). The expected behavior is that benchmark-on-device jobs should either not be scheduled or be marked as skipped/canceled if a dependent job, such as export, fails.
2. In the export-models job, the error in "Upload artifacts to S3" step is misleading. It should be marked as skipped or canceled, as the "Run script in the container" step failed to generate the .pte file (highlighted in the yellow box).

cc: @huydhn @cbilgin @digantdesai @kimishpatel

Versions

trunk

cc @huydhn @kirklandsign @shoumikhin @mergennachin @byjlw

[guangy10]

@yangw-dev There is another tiny improvement we can make. As shown on the screenshot, there are two entries for "iPhone 15". They are actually different, one is running on iOS 18, and the other one is iOS 17. We should considering adding the major.minor os version to avoid confusion and improve the logging readability. cc: @huydhn

[huydhn]

Given that there is an issue where timing out job won't print anything. I'm tempted to split this part into 2 steps:

1. Run the benchmark
2. Print the spec outputs. The second step will also be done even if the first step timeout. This will also help make the spec output easier to view.

Thoughts?