Finalize DestroyInvalidMembers migration

What does this MR do and why?

Describe in detail what your merge request does and why.

1. Add a temp index on null member namespace id so we can use it later: !100123 (merged) ✅
2. Delete the migration that used the less performant column: !99231 (merged) ✅
3. Create new migration using the more performant column and index with a later timestamp !99467 (merged) ✅
4. Finalize migration !99080 (merged) (this MR)
5. Drop the temp index

main: == 20221006070927 FinalizeInvalidMemberCleanup: migrating =====================
main: == 20221006070927 FinalizeInvalidMemberCleanup: migrated (0.0149s) ============

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.