Improve look of listviews for projects, texts, Q's

Instead of presenting projects, texts and questions as a table view
suitable for editing, we should present them in a view more like the
design of the spec.

There's quite a bit of fake data being presented here, like the number
of questions per text, unread answers, unread comments, and so on.
Eventually this will be turned into real API calls, but for now this
gives us a page to look at that closely resembles the real thing.
Make the fake data look subtly wrong

I decided to make all the numbers in the fake data negative. That way
they look almost-but-not-quite right, and once the real API calls are
written it will be obvious when the fake data is replaced by real data
because the numbers will start turning positive. (Or zero).
Make CSS for active listview "rows" more generic

Instead of specifying that only <tr> tags with the "active" class
will be highlighted, the listview CSS should highlight *any* element
inside the listview with a class of "active". This allows for, say,
unordered lists to be used to lay out listviews.
Restore remove button back in projects, texts, Q's

Eventually the button (and the checkboxes that go with it) should be
made visible and available, or hidden and unavailable, depending on
whether the logged-in user has appropriate admin rights. For now,
they will just be visible to all users.
Merge branch 'feature/checks'
Merge branch 'master' into feature/questiondto