Improve test result and log presentation in the dashboard

## Context

Recent user feedback exposed several presentation issues that make test results harder to understand.

Examples include:
• Long test names are truncated even when the distinguishing portion is near the end of the name.
• “No logs available” may be displayed even when related log artifacts exist in the output files.
• Build-related kselftest results can be mistaken for executed test results.
• Users may have difficulty understanding where the complete build or test logs are located.

During our own investigation we reproduced the long-name problem with paths under kselftest.exec.exec_check-exec-tests_sh, where the paths share a long common prefix and the distinguishing suffix can be hidden by truncation. This shows that simply increasing column width may not be sufficient.

## Goal

Improve the presentation of test results and logs so users can clearly understand what a result represents and access the available artifacts.

Initial items / points to discuss
• Improve handling of long test names, considering wrapping, tooltip/full-name access, expansion, or a hierarchical representation.
• Avoid hiding the significant suffix of long names.
• Review the “No logs available” state when output log artifacts exist.
• Make build results versus executed test results clearer.
• Make available log/output artifacts easier to discover.
• Review whether filters/navigation can produce confusing combinations of tree/configuration results.

No files, tests, or entry points are named in the issue. Start by locating the dashboard views that present test names, results, and log artifacts, then define done as making long names understandable, distinguishing build from executed results, and exposing available logs without misleading empty states.

Written by the indexing model from the issue text.