The repo home batches its visibility, sealed and issue-by-id probes for pulls and runs #6819

The repo home (/<owner>/<repo>) runs three statements once per visible pull or run instead of once per page: the repo-visibility check (SELECT 1 AS n FROM repo WHERE repo.id = ?1 AND NOT EXISTS ...), the sealed check (SELECT sealed, author_id FROM issue WHERE id = ?1) and the issue-by-id read. With 200 issues, 40 pulls and 5 runs the page costs about 50 more statements than with a handful of rows.

test/app-home-batched.test.ts leaves them out of its count through PER_ROW_TODAY. Batch them, then delete that list: the test then holds every statement to the same count at both sizes.

Found while fixing #6815.

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.