Consider move `hasTrace` logic to the backend & show new illustration when job is running and has no trace yet
### Problem to solve
(What problem do we solve?)
### Further details
The following discussion from gitlab-ce!22087 should be addressed:
Scoped off from [discussion](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22087#note_106335382): (+6 comments)
### Proposal
Consider move `hasTrace` logic to the backend & show new illustration when job is running and has no trace yet
In order to avoid a lot of logic on Frontend we should consider move
```
export const hasTrace = state => state.job.has_trace || state.job.status.group === 'running';
```
to the backend
### Solution
#### UI
[illustrations_running-job_no-log.svg](/uploads/5b1500acde21e28cc0e32ac4cb320451/illustrations_running-job_no-log.svg)
Illustration merge request: https://gitlab.com/gitlab-org/gitlab-svgs/merge_requests/171
Copy: `This job has started but the trace is not yet available`
### What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)
### Links / references
issue