Unnecessary error logging when cleanbanning a banned user
Sentry Issue: [BOT-2ZT](https://sentry.io/organizations/python-discord/issues/3092995113/?referrer=github_integration)

```
Failed to apply ban to user xxxxxxxxxxxxx
```

See https://github.com/python-discord/bot/blob/f9fff6eaae409c7ba12ea6f95873aa0fd0340554/bot/exts/moderation/infraction/infractions.py#L125

I think this happens when a user is cleanbanned after being banned. We can probably just remove this `log.error` as `apply_ban` already does it's own logging.

*Opened by wookie184*
diff --git a/bot/exts/moderation/infraction/infractions.py b/bot/exts/moderation/infraction/infractions.py
index 88129840..60b4428b 100644
--- a/bot/exts/moderation/infraction/infractions.py
+++ b/bot/exts/moderation/infraction/infractions.py
@@ -126,8 +126,6 @@ class Infractions(InfractionScheduler, commands.Cog):
         infraction = await self.apply_ban(ctx, user, reason, duration_or_expiry=duration)
         if not infraction or not infraction.get("id"):
             # Ban was unsuccessful, quit early.
-            await ctx.send(":x: Failed to apply ban.")
-            log.error("Failed to apply ban to user %d", user.id)
             return
 
         # Calling commands directly skips discord.py's convertors, so we need to convert args manually.
['bot/exts/moderation/infraction/infractions.py']