address performance issues with /tests and /targets views

[trey-ivy]

when running in an environment where target entries scale and become very large, the pass rate functionality can cause the targets and tests views to become slow and unresponsive. to address this issue, i'm removing pagination, avg/min/max duration and pass rate from these views and adjusting the backend queries respectively to see if this improves performance enough to make the application more responsive. I'm also adjusting the cache policy from cache and network to the default and adding a long poll interval and indexing the label fields of target pair and test collection in the db. In a subsequent PR, I will add avg/min/max/passrate/# runs to the test details view.

additionally, adding the pprof endpoints to help performance tuning in the future

[trey-ivy]

the new views look different, but i don't think we're losing that much functionality. idk how useful it was to have avg/min/max/passrate/#runs on the list view. The idea was to implement sorting at some point to allow you to find things like your longest running jobs and most built targets/etc. I'm still going to provide this data but it won't be pulled real time. it will be calculated daily and moved to the trends view. You can of course still write a custom query to pull the data from the graphql api, but the performance hit was causing views to break and become unresponsive.