automod: identical reply rule (#466)
Two enabling features:
- cheap consistent non-cryptographic-strength hashing of strings for use
in counter keys (went with uint64 murmur3, which was already in
dependency tree)
- ability to increment a counter for a single time period, to control
counter key space growth (for redis)
This initial version of the rule counts replies to any other user in the
same bucket, not distinct-accounts-with-same-reply-text. I'm a little
worried about redis memory growth if we have a HyperLogLog for each
author+text combination (as opposed to simple counter int). Maybe the
redis implementation is clever and efficient for the small-distinct
case? Or maybe RAM is cheap enough?
This branch will conflict with
https://github.com/bluesky-social/indigo/pull/464. Plan to merge that
one first, then i'll rebase this one.