Task was destroyed but it is pending: WebsocketImplProtocol.async_data_received (Sentry-wrapped)

### How do you use Sentry?

Sentry Saas ([sentry.io]())

### Version

2.43.0

### Steps to Reproduce

Hi team!

I'm having quite a few errors like these popping up in my Sentry account. At first, I thought it was an issue with my Websocket implementation, but looking at the stacktrace, some of the errors are from a standard GET request, such as this one:
[https://cnicodeme.sentry.io/share/issue/7f8aa28baa194938bd13f44953014819/]()
(For the Sentry team, feel free to access this ticket, and all the other that have the "Task was destroyed but it is pending" currently open in my organization).

I suspect that the Sentry system doesn't have the time to send the data to [Sentry.io]() and is killed before, somehow.
Unfortunately the error doesn't contain the original one, making it harder to trace where it originated and/or fix it.

### Expected Result

It shouldn't throw a "Task was destroyed but it is pending" but instead the actual underlying error. I suspect the task of sending that error to Sentry is killed before it has the chance to deliver the payload.

### Actual Result

I'm using Sanic 24.6.

Happy to share anything more that is needed