Add initial implementation of new builds list for experimental Job UI

[janfaracik]

This is a very rough version of the builds list, with the intention of iterating heavily later.

What's new

• Larger cards, bigger clickable surface area
• Integration with our App Bar API (e.g. you have access to all build actions on its row now)
• Build details now appear on the row

Future iterations will include

• Smarter displaying of details (we currently show all, that's not particularly helpful)
• Pagination
• Searching and filtering beyond what we can do now
• Plugin integration (e.g. Pipeline Graph View can surface its stages as part of a build)
• I18n

Testing done

• Builds display
• Legacy UI isn't impacted by this change

Screenshots (UI changes only)

Before

After

Proposed changelog entries

• Add initial implementation of new builds list for experimental Job UI

Proposed changelog category

/label web-ui,rfe

Proposed upgrade guidelines

N/A

Submitter checklist

• The issue, if it exists, is well-described.
• 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.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin. In particular, 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).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

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

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• 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).
• If it would make sense to backport the change to LTS, be a Bug or Improvement, and either the issue or pull request must be labeled as lts-candidate to be considered.

[timja]

I'm not sure this is useful, why would you need to take actions like replay on any build other than the latest or so? Its quite distracting seeing all that green.

Overflow menu should be fine for actions?

[janfaracik]

That's a fair comment! I've updated it so we just show the overflow menu.

[timja]

update screenshots?

[janfaracik]

✅