I went ahead and removed that one for you. I’ll also be releasing a fly ext sentry destroy command to help with this in the future.
A note on why this happens: we keep a local record of every extension, including Sentry projects, and names in our systems must be unique per-provider.
We never added destroy because Sentry’s API doesn’t allow deleting the remote project on Sentry.
However, you projects names in Sentry don’t need to be unique. So there should be no harm is allowing users to delete Sentry projects on Fly.