Implement ingesting modlog actions

[FoxxMD]

TODO:

• Determine if CM should react to modlog events as first-class citizen (like comment/submission) or react to them like a modifier (source, dispatch)
• Check/verify if modlog can be a shared source
• ???

[CryptoMaximalist]

In case your link was requesting me to log my request here:

One way I've kept API and network activity lower on my bots is to rely on mod log data to keep my cache fresh between daily updates. Here are a few examples:

• Watch the modlog for edits to the CM config page and kick off an update instantly rather than waiting 5 min
• Download a list of mods and contributors(approved users) daily, then throughout the day use the mod log to update this cache. I would love to exclude my checks from running on these "whitelisted" users, but didn't want to use the API call to check.
• Watch for ModNote log entries and perhaps they have enough info to avoid pulling Notes during event processing.
• Unfortunately the UserNotes log entry is just a wiki edit without the actual note in it, but that's not useless. If the modlog does signal changes to a user's UserNotes, CM knows to pull a fresh version of their notes. If there have been no modlog entries for the user since the UserNotes were cached, it knows the cache isn't stale.