New firehose endpoint uses the top feed algorithms to deliver reserved entities for users to moderate.
New managers and repositories for talking to elastic search via the top feed managers Redis lock system with some super fast hash keying. These records shouldn't get very big, so we might want to KISS for now. Else, there are distributed locking libraries we should look into
It stores a key in as set entity_id:user_id format where the entity is the activity being moderated and user is the admin who "checked it out". These are set to a TTL of 10 minutes for now. When we query elastic search, we look for the opposite set (any locks that DON'T belong to the user) and for any activity that has not already been moderated. Requires adding two new fields to badger (in postman)