Finalize member namespace id cleanup

What does this MR do and why?

Describe in detail what your merge request does and why.

Issue: #365029 (closed)

To ensure that !95881 (merged) and !80253 (merged) completed successfully on self-managed instances, we need to also finalize this migration.

main: == 20220913082824 FinalizeInvalidGroupMemberCleanup: migrating ================
main: == 20220913082824 FinalizeInvalidGroupMemberCleanup: migrated (0.0089s) =======

ci: == 20220913082824 FinalizeInvalidGroupMemberCleanup: migrating ================
ci: -- The migration is skipped since it modifies the schemas: [:gitlab_main].
ci: -- This database can only apply migrations in one of the following schemas: [:gitlab_ci, :gitlab_shared, :gitlab_internal].
ci: == 20220913082824 FinalizeInvalidGroupMemberCleanup: migrated (0.0001s) =======

main: == 20220914070927 FinalizeInvalidProjectMemberCleanup: migrating ==============
main: == 20220914070927 FinalizeInvalidProjectMemberCleanup: migrated (0.0158s) =====

main: == 20220913082824 FinalizeInvalidGroupMemberCleanup: reverting ================
main: == 20220913082824 FinalizeInvalidGroupMemberCleanup: reverted (0.0008s) =======

main: == 20220914070927 FinalizeInvalidProjectMemberCleanup: reverting ================
main: == 20220914070927 FinalizeInvalidProjectMemberCleanup: reverted (0.0008s) =======

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.