The issue summary table was looping over all the entries, checking if they were

reviews, then looping over all the comments therein, checking if there's an

open issue, and finally rendering stuff. This was overly complex, and will get

even more so once entries other than review boxes can contain issues.
Since we're already processing all the comments in the ReviewRequestPageData

object, we might as well aggregate all of the ones with open issues into a

list, and just use that.

Verified that the issue summary table displayed the same as before.