Test ee/spec/features/registrations/identity_verification_spec.rb

What does this MR do and why?

Require solved Arkose challenge before phone or credit card verification

Previously, both Arkose challenge and reCAPTCHA were used to prevent automated attacks on phone number and credit card verification endpoints.

These challenges were required only when specific rate limits were exceeded. For example, users were required to solve an Arkose challenge before they were allowed to send or validate a phone number verification code after two previous attempts. ReCAPTCHA was required, replacing Arkose challenge, for the same operations when Telesign transactions exceeded 16k for the current day.

In this commit, the challenge requirement is simplified such that users need to solve an Arkose challenge before they are allowed to send a phone number verification code (challenge requirement to perform code verification is removed) or verify their identity using a credit card. Users that are required both phone number and credit card only need to solve the Arkose challenge to perform whichever verification method comes first. Finally, ReCAPTCHA is no longer utilized.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

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

Before	After

How to set up and validate locally

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