When you "dev_block" something, have that inject a "synthetic" but
out-of-date CR signature in the UI. This means that a dev_block somewhat
reserves a place for you to CR it in the future.

Most dev_blocks come after a review and we generally presume that the
dev blocker will come back and CR it after the requested changes have
been made. Therefore, we now show a dev_block as an "inactive" CR.

Also, move the typescript comment to the line it's referring to.

Closes #193

Since a dev block may be made by someone QAing or CRing, and will
usually end up requiring further CR and QA by the same people, let's
render a dev block as an out of date CR + QA.

This change counts a block as a CR and QA as far as the leader board is
concerned