Add last build status to job page

[janfaracik]

Small PR to add the latest build status to the job page, making it consistent with the build pages/dashboard table. Drops the project prefix as its unnecessary. Also tightens up the appearance of the app bar/build caption combination, adjusting the size of the icon and text to make it more visually balanced.

Testing done

• Build status is shown on the job page
• Icon hides when there are no builds

Proposed changelog entries

• Add last build status to job page

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@jenkinsci/sig-ux

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[yaroslavafenkin]

Looks OK security wise

[janfaracik]

@jenkinsci/sig-ux Could I get another look on this? Thanks! :)

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

[basil]

Caused jenkinsci/acceptance-test-harness#1296.

[basil]

Caused jenkinsci/acceptance-test-harness#1300.

[uhafner]

On the build page the icon is now selectable but does nothing when clicked. Wouldn't it make sense to either remove the clickable (and selectable) state or navigate to the console log (as in the build history)?