EventStreams: Change used streams to make redirect filtering work

[stjohann]

The biggest current problem with EventStreams implementation is that --type new streams do not have any access to data about whether a page is a redirect or a legitimate page. At best, there is auto-filled summary that can potentially be ignored.

There can be some things done to fix this, but it requires too much effort from me right now. Rough

1. See how different streams correspond in terms of available data.
2. Figure out whether the transition to another stream(s) by default could be something viable, even only for page creations or page edits.
3. Implement the code for different EventStreams schemas if they would provide more options for filtering.
4. Implement new filters augmented by new data (--redirect true/false/null for one, --usergroup autoreview might be another example), while still supporting all the old ones.
5. (Optional) Implement a way to display log actions (categorise is useless given Discord rate limits IMO).

IIRC page-create stream can provide more data than recentchange stream I am using for everything right now, so there definitely might be something there. You can pass and parse multiple streams (like /page-create,recentchange), so that is not a concern. At the same time, this issue is still more of a problem statement and I do not have time or will to work on this myself yet.