Update Trove's dashboard
Update Trove's dashboard

This change set updates Trove's dashboard to reflect several changes
in the project, and the way in which we have, as a project been
handling our priorities.

The changes are summarized below:

- The Trove project now includes the trove-dashboard, we use
  trove-specs for specs, and code is in trove, trove-integration and
  python-troveclient. All five repositories must be considered in the
  dashboard.

- There has been an ongoing issue with review aging and it is
  important to highlight reviews that have been around for a while and
  need priority attention.

- We have, as a project, been using the starredby:<PTL> as a way to
  indicate reviews that are a priority for the team. This is
  particularly the case close to the release milestones. This means
  the name of the PTL is unfortunately part of the dashboard but there
  appears to be no easy way around this as illustrated by the
  responses to ML threads on this subject, for example [1].

- Changes on branches other than stable must also be highlighted and I
  feel that this is particularly the case in the context of the
  current development cycle for Newton and the number of changes that
  will likely be sent to Mitaka and Liberty as well.

- Specs and code requiring review have been called out independently,
  and the code requiring review has been broken up between the client
  (python-troveclient and dashboard) and the server (trove and
  trove-integration)

- A number of patches often end up in merge conflicts, with gate and
  check failures, and otherwise in need of attention and these are
  being called out in a section of their own.

- Finally, I've retained the section of changes requiring final
  approval as this is a driver for core reviews.

[1] http://openstack.markmail.org/thread/s2uc4ezrkwb7spzr

Change-Id: I622bd832550ca1efc554d952ab892120e9a4817f

Frostman/gerrit-dash-creator,Frostman/gerrit-dash-creator,stackforge/gerrit-dash-creator,Frostman/gerrit-dash-creator