So it's more accessible for views to access the names of jobs.
Only filter Build#name from where we really need to download it.

It doesn't make too much sense having this standalone

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5142#note_13058785

And note that job/build_name could contain `/`

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5142#note_13047190

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5142#note_13047184

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5142#note_13047163

Basically:

    GET /api/projects/:id/artifacts/:ref_name/:build_name

Also added tests for it.

It turns out they are different:

    builds.success.latest.first

and

    builds.latest.success.first

If we put success first, that latest would also filter via success,
and which is what we want here.

* upstream/master: (117 commits)
  spec and fix for sanitize method
  remove fix validatable import url migration
  Fix typo in spec
  Update Gemfile.lock after versions were added in !5078
  Add more comments to regex
  Add changelog item
  Add blockquote fence syntax to Markdown
  Fix typo and explain the precedence of STDERR and STDOUT
  Add changelog entry for !4399
  Add reminder to not paste private SSH keys
  Make subnavigation a bit darker color
  Update ui_guide.md with button capitalize rule
  Re-use queries in reference parsers
  Use btn-danger for delete button.
  Update New Snippet buttons.
  Run bundle install.
  Add min attribute to project_limit field on user's form
  Wrong gitlab-shell version
  API: Expose shared projects in a group
  Memoize MR merged/closed events retrieval
  ...