patch(robo): prevent endless spam in debug messages

[Pkmmte]

Sage debug messages are great but sometimes they can be a bit... spammy.

Let's say you have an error inside a messageCreate event and that triggers an error in that same channel, that error message itself also triggers an error, and so forth infinitely.

We should detect when an error is a duplicate and sent within a short timespan (< 1 minute), then artificially cap it after 3 attempts, with the Robo sending a "capped" message as the third.

---

Changeset: minor