cleanup: add an ORDER BY clause to EventTag
cleanup: add an ORDER BY clause to EventTag

Without this, Postgres tries to do a sequence scan, which is fine in
most cases. The case where this falls apart is when there are less than
10,000 rows matching, and then ends up sequence scanning the entire
table. The explicitly ORDER BY coerces Postgres into always using the
date_added index.

mvaled/sentry,looker/sentry,beeftornado/sentry,jean/sentry,mvaled/sentry,mvaled/sentry,ifduyue/sentry,looker/sentry,gencer/sentry,jean/sentry,ifduyue/sentry,gencer/sentry,jean/sentry,gencer/sentry,gencer/sentry,ifduyue/sentry,beeftornado/sentry,beeftornado/sentry,looker/sentry,mvaled/sentry,ifduyue/sentry,ifduyue/sentry,looker/sentry,jean/sentry,jean/sentry,gencer/sentry,looker/sentry,mvaled/sentry,mvaled/sentry