Targets Exploration View, Problems Tab Updates

[trey-ivy]

Currently, when you have large builds w/several invocations displayed in a single build view, if the problems tab contains lots of debug data, it can cause the view to hang forever and/or crash the view. The problems view contains helpful data, but it does not necessarily need to be the default tab for an invocation. Adding an 'overview' tab allows us to dynamically load the 'problems' data only when requested (i.e. when the user clicks the tab). This clears up the issue with builds, provides faster loading times, and gives us the ability to key in on other useful data in the overview tab.

invocation overview tab (dynamically hide problems tab for successful builds)

problems tab moved to the end and displayed dynamically (spinner while loading)

the display issue for remote blobs still remains.

Target exploration and the ability to chart target build time extends the same base functionality found in the /tests route to a /targets route. Since tests are targets, just with more data, we may want to look at consolidating these views at some point as well, but for now, just giving the ability to view the historic trend data for a given target will be useful.

targets exploration view

targets pass/fail grid

targets details view

• updates schema to add order by functionality to targetpair entity
• add graphql api methods for getting target data
• decouple problems data from bazel invocation view data
• targets and targets/[slug] routes and views
• targets exploration views and components
• extend custom schema with target display associated types
• update golden files for testing