feat: implement multi step registration experiment

[syedsajjadkazmii]

Description

This PR implements a Multi Step Registration A/B experiment

Control Variant: Registration form with 2 steps. (Name, email and password on first step. Username and country of second step).
Multi-step registration variant: Registration form with 3 steps. (Email field on first page. Name and password on second page. Username and country on 3rd and last page).

JIRA

VAN-1902

How Has This Been Tested?

Locally

Screenshots/sandbox (optional):

Variation:

Screen.Recording.2024-04-16.at.4.56.39.PM.mov

Control:

Screen.Recording.2024-04-16.at.4.54.14.PM.mov

Merge Checklist

• If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Sandbox, if applicable.
• Is there adequate test coverage for your changes?

Post-merge Checklist

• Deploy the changes to prod after verifying on stage or ask @openedx/2u-vanguards to do it.
• 🎉 🙌 Celebrate! Thanks for your contribution.

[mubbsharanwar]

How would we activate the experiment or get the variation on the backend to enable the autogenerated username flag in case of variation?
If we use the full stack optimizely experiment the user would not be authenticated when lands on the registration page where we are activating the experiment. How can we use optimizely full stack, I mean I think optimizely full stack requires only authenticated users to activate the experiment.
Please correct me if my understanding is wrong about the full stack optimizely.

[syedsajjadkazmii]

How would we activate the experiment or get the variation on the backend to enable the autogenerated username flag in case of variation?
If we use the full stack optimizely experiment the user would not be authenticated when lands on the registration page where we are activating the experiment. How can we use optimizely full stack, I mean I think optimizely full stack requires only authenticated users to activate the experiment.
Please correct me if my understanding is wrong about the full stack optimizely.

We are not hiding username, we are just moving it 3rd step. So no need to autogenerate username

[mubbsharanwar]

How would we activate the experiment or get the variation on the backend to enable the autogenerated username flag in case of variation?
If we use the full stack optimizely experiment the user would not be authenticated when lands on the registration page where we are activating the experiment. How can we use optimizely full stack, I mean I think optimizely full stack requires only authenticated users to activate the experiment.
Please correct me if my understanding is wrong about the full stack optimizely.

We are not hiding username, we are just moving it 3rd step. So no need to autogenerate username

Oh, I missed it. got it, thank you!

[mubbsharanwar]

LGTM.