[Clean up] exit_registration_verification

Summary

This issue is to cleanup (REMOVE) the exit_registration_verification feature flag. As per @alexbuijs's comment:

This was part of the require_verification_for_namespace_creation experiment. Both were never enabled, unfortunately. So I think it's save to remove both in tandem completely!

Owners

• Team: Activation
• Most appropriate slack channel to reach out to: #g_activation
• Best individual to reach out to: @alexbuijs
• PM: @p_cordero

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

As per this conversation we're ready to clean up this Feature Flag

• Create a merge request to remove <feature-flag-name> feature flag. Ask for review and merge it.
  • Remove all references to the feature flag from the codebase.
  • Remove the YAML definitions for the feature from the repository.
  • Create a changelog entry.
• Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post.
  • /chatops run auto_deploy status <merge-commit-of-cleanup-mr>
• Close the feature issue to indicate the feature will be released in the current milestone.
• If not already done, clean up the feature flag from all environments by running these chatops command in #production channel:
  • /chatops run feature delete <feature-flag-name> --dev
  • /chatops run feature delete <feature-flag-name> --staging
  • /chatops run feature delete <feature-flag-name>
• Close this rollout issue.