Update yelling.py

[bradleysigma]

The UQCS #yelling tradition dates back to May 2019, in the days of the UQCS Slack, and bot functionality was added in September that same year. It was carried over to Discord early in the migration process. Due to Discord permissions, however, some members cannot have a timeout applied by the bot.

In April, May, and June of this year, there were nine members who triggered the yelling functionality of the bot ten or more times. Of these, four had some sort of role that exempted them from the time out; specifically, they were either committee members or subcommittee members. Given that such members make up a vast minority of UQCS members, this would indicate that such members would be wildly more likely to trigger the yelling functionality of the bot. Anecdotally, these members also seemed to me to be more likely to send multiple messages in a row that would trigger the yelling functionality.

I believe that the tradition works best when everybody participates, and are in on the joke, and as such, nobody should be immune from the yelling functionality. The timeout cannot be applied to these members, and rearranging roles to allow the timeout to be applied would cause more problems that it would solve. Instead, this PR will add an alternative "punishment", in the form of additional chastisement, to anybody who the bot fails to time out.

During a previous PR addressing the same issue via a different method, concerns were raised that occasionally, committee members would need to send serious messages in #yelling, and the method used in that PR would jeopardise this. Such a scenario seems rare enough that I cannot recall any instances, but nonetheless, it should be borne in mind. This PR will cause the bot to send two messages instead of one, so the structure of #yelling won't change. Should a committee member need to send serious messages, then the current process should suffice for if this PR is implemented. I would suspect the process would be to delete the bot's reply message to any serious messages sent, in which case the committee member would just need to delete two messages instead of one.

[JamesDearlove]

IIRC, we should have somewhere an example to use role lookup rather than embed the committee role ID. Could we use something like that instead? Mainly so it won't break on testing server

[bradleysigma]

@JamesDearlove, done, based off of advent.py.