Performance: Make tenant delete faster and more robust

[robotdan]

Make tenant delete faster and more robust

Description

Deleting a tenant with 10-20M users can take a bit of time.

I think there is room for improvement here. A couple of ideas:

1. Allow all processing to be disabled on a Tenant delete, no webhooks, no re-indexing, just brute force delete, and then do an re-index at the end.
2. Review the current delete strategy to see if there are opportunities for improvement. This currently uses a similar strategy to the re-index, however because we have to add the tenantId to a WHERE clause, this affects the SELECT. It may be better to not use a cursor in this path.

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.