The Issue Summary Table was managed within ReviewRequestEditorView,

but it only existed on the review request page. This meant that the

editor had to conditionally manage the table, which wasn't really

necessary.
The table is now managed by the review request page's view instead. Like

other views in reviewRequestPage/, this now has a

RB.ReviewRequestPage. prefix, helping to keep it organized and its

purpose clear.

Tested that the issue summary table still loaded and that all filtering

worked. Also tested that clicking an issue caused the appropriate entry

box to expand.