Cache the number of patrons in the participants table

This is a performance improvement. We're already caching the `receiving` amount of participants, so adding the number of patrons is pretty easy.
Ah, I had assumed it was a Postgres thing. I should've looked closer; it's obvious now what's happening.