chore: prune the token whenever we receieve a 403

[Gustrb]

Proposed changes (including videos or screenshots)

Whenever we try to send a push notification to a stale token, we get the SENDER_ID_MISSMATCH, and we should prune it from our database so we don't keep trying to send to those tokens. This happens when the user has to regenerate their credentials, which had to happen in order to migrate the legacy push notification provider to FCM. Here the approach is similar to: https://github.com/thingsboard/thingsboard/pull/10679 Related issue on that codebase: https://github.com/thingsboard/thingsboard/issues/10602#issuecomment-2085452463

Issue(s)

Steps to test or reproduce

Further comments

CONN-376