Automate the emoji suggestions workflow

[SuperSajuuk]

At this time, the current workflow for blob suggestions goes like this:

• User uploads a suggested blob into the suggestions channel, this is then posted to council-queue
• The council decide whether it's a good blob or not. If council says it's good, they vote yes and then it's moved to public queue.
• When moved to public queue, the public vote on the suggestion. After a few days, if the public majority agrees to add the blob, Wolfiri (or another police) makes sure and then uploads to a server.

While this is ok, this can slow down the addition of new blob suggestions, especially as they have to be uploaded to another server that users need to be a member of. This also means police then have to find the user who had their suggestion approved and then add the Blob Maker role.

An ideal solution would be to automate the whole queue, so that police aren't involved so heavily on uploading the emoji, but still retaining oversight. In this idea, the ideal workflow is this:

• User uploads a suggested blob into the suggestions channel, this is then posted to council-queue
• The council decide whether it's a good blob or not. If council says it's good, they vote yes and then it's moved to public queue.
• When moved to public queue, the public vote on the suggestion.
• The bot will then track all reactions added: if more than X total reactions have been added, and there are Y more approvals than denials, the bot tells police they need to vote to add the bot. EG 750 total reactions, with 200 more approvals than denials
• Once blob police have been notified, they then do reaction votes: 4 approvals and the emoji is uploaded to a server and the submitter gets the role. 4 denials and the emoji is rejected and the user informed. (I do not generally expect that an emoji that reaches this point would ever be denied, but that option should be there, in the case of shitpost/meme-based blobs)

The numbers would be changeable of course, this is just to give an idea of what the ideal flow would be. Automating the workflow gives us more choice to make a bunch of stats from each stage and, in addition, would tie in nicely with ticket #8.

[slice]

FYI: The bot already tracks upvotes/downvotes (not individually) in the public queue, it just doesn't do anything with those metrics.

[slice]

Oops.