Listing: use same buttons pattern for builds and versions listing

[humitos]

I think we have been happy with the pattern we have in the version listing with those buttons at the right:

Today I found that those buttons are different in the build listing page but it seems we should be able to use the same pattern:

Why we don't we move the content from the chip into the list item? The "Book" icon could be a button, similar to the version listing page, and the other two links could be inside the "..." (dots) dropdown. That way we remove the extensive usage of chips that require hovering --which is usually harder than just a simple click.

[agjohnson]

We shouldn't alter the version popupcard. The intention with that UI is not to supplement UI in the build listing view. Instead the buttons should exist in both, it sounds like mostly just a view docs button that we should add to the buttons list.

A few things there:

• We don't have the URL of the built documentation and this is a slow query. In other UIs, this is an async call against APIv3 on buttons hover.
• There are probably issues with the API used here. It might be stuck using APIv2, if at least for reasons like
  • API: using private API endpoints on public listing pages #154
• If we can use APIv3 we should have the resolved URL already, if not we might be stuck with what APIv2 can give us.
• That resync button uses APIv3 now at least.