Run AutoMod-blocked messages through autowarn filters

[FloatingMilkshake]

This PR closes #209.

Runs messages that are blocked by AutoMod through our typical autowarn filters. This means users will be automatically warned for messages that would typically trip Cliptok's filters, even if AutoMod blocks the message from being sent first (currently this results in Cliptok not even seeing the message). This includes filters, like unapproved invites, mass emoji, scam checks, etc., but not 'passive' checks like user tracking*, passive list tracking, etc.

*Blocked messages will still end up in user-tracking threads in some way. It looks like this is just a blank embed pointing to the #investigations AutoMod message. This is because that message causes a Message Create event to be fired, and that is what makes it through to the tracking thread! I was initially not sure what to do about this, but I decided to leave it because I think it fits, considering how the point of the thread is to track all of the messages sent by a user.

AutoMod events don't give us a DiscordMessage, so this was a little awkward to do. I chose to create a fake MockDiscordMessage with the properties from the AutoMod event, and adjusted things like the message handler to accept that instead of DiscordMessage (there are now two overloads—one that takes a MockDiscordMessage and does the handling on that, and one that takes a DiscordMessage, throws its data into a MockDiscordMessage, and passes that to the other overload—this way there's no trouble when trying to use a regular DiscordMessage. I also did this for the DeleteAndWarnAsync and MessageLink methods).

One thing I'm not sure about is the phrasing for when a user is pardoned the first time they send a message containing too many emoji or lines. For example, you can see here:

Cliptok/Events/MessageEvent.cs

Lines 488 to 491 in dff0e2a

	if (Program.cfgjson.UnrestrictedEmojiChannels.Count > 0)
	msgOut = await message.Channel.SendMessageAsync($"{Program.cfgjson.Emoji.Information} {message.Author.Mention}, if you want to play around with lots of emoji, please use <#{Program.cfgjson.UnrestrictedEmojiChannels[0]}> to avoid punishment.");
	else
	msgOut = await message.Channel.SendMessageAsync($"{Program.cfgjson.Emoji.Information} {message.Author.Mention} Your message was automatically deleted for mass emoji.");

...and here:

Cliptok/Events/MessageEvent.cs

Lines 623 to 627 in dff0e2a

	if (!Program.db.HashExists("linePardoned", message.Author.Id.ToString()))
	{
	await Program.db.HashSetAsync("linePardoned", member.Id.ToString(), false);
	string output = $"{Program.cfgjson.Emoji.Information} {message.Author.Mention}, your message was deleted for containing too many lines.\n" +
	$"Please consider using a Pastebin-style website or <#{Program.cfgjson.UnrestrictedEmojiChannels[0]}> to avoid further punishment.";

...that the user sees a message like "Your message was deleted for mass emoji." I don't want to change that to "Your message was blocked ..." because the reason for the block might not be mass emoji—it could be something else, but Cliptok could be acting on mass emoji anyway. Open to suggestions on how this could be changed! :P

[Erisa]

Looks good, just one nitpick in the comments.

re: wording, I think it's best to be generic instead of situational with these.

"Play around with lots of emoji" can stay as-is.

then:

-     msgOut = await message.Channel.SendMessageAsync($"{Program.cfgjson.Emoji.Information} {message.Author.Mention} Your message was automatically deleted for mass emoji."); 
+      msgOut = await message.Channel.SendMessageAsync($"{Program.cfgjson.Emoji.Information} {message.Author.Mention} Your message contained too many emoji."); 

-      string output = $"{Program.cfgjson.Emoji.Information} {message.Author.Mention}, your message was deleted for containing too many lines.\n" + 
+      string output = $"{Program.cfgjson.Emoji.Information} {message.Author.Mention}, your message contained too many lines.\n" + 

but also, can we please make the too many lines not offer the chance to show the full message, specifically for automod checks? It runs after other checks for a similar reason, which is to not act as an automod bypass opportunity.

[FloatingMilkshake]

then:

-     msgOut = await message.Channel.SendMessageAsync($"{Program.cfgjson.Emoji.Information} {message.Author.Mention} Your message was automatically deleted for mass emoji."); 
+      msgOut = await message.Channel.SendMessageAsync($"{Program.cfgjson.Emoji.Information} {message.Author.Mention} Your message contained too many emoji."); 

-      string output = $"{Program.cfgjson.Emoji.Information} {message.Author.Mention}, your message was deleted for containing too many lines.\n" + 
+      string output = $"{Program.cfgjson.Emoji.Information} {message.Author.Mention}, your message contained too many lines.\n" + 

but also, can we please make the too many lines not offer the chance to show the full message, specifically for automod checks? It runs after other checks for a similar reason, which is to not act as an automod bypass opportunity.

Done! Good thinking with the automod bypass catch, that obviously didn't occur to me 😅

[Erisa]

lgtm, merge when ready. The bug with some automod events not working correctly doesn't have any catastrophic consequences and doesn't appear to be the fault of this code.