With customizing first cryptobot, build incentive first -> then do authentication + claiming steps later

## Problem Description:

After completing Module 0, to start customizing their personalized cryptobot one needs to do the following:

1. Install Temple Wallet -
- takes like 5 mins with a lot of cognitive load
- breaks the flow user is in when they were expecting to get their cryptobot

2. Give their email + verification through Magic flow
- takes like 2 mins
- breaks the flow user is in, especially when they have like 3 tabs open:
- 1 tab on which Cryptoverse Wars is saying do the Magic flow.
- 1 tab to open the email
- 1 tab on which Magic verifies and tells you to go back to Cryptoverse Wars.
- for the privacy-conscious and anon community members, this becomes a blocker.

Given the user has not even customized anything and we start asking for so many things, this will lead to a lot of dropoff.

## Proposed Solution:

- Instead of doing all these things before customizing, do these steps after the user is happy with the customization so they have enough incentive to do the rest of the steps.
- Provide people with the mechanism to opt-out of the magic process for privacy-conscious people.

Start by mapping the flow after Module 0, including Temple Wallet installation and Magic email verification. Determine where customization is blocked by these steps and define done as letting users customize before authentication and claiming, while providing the proposed Magic opt-out for privacy-conscious users. The payload names no files or tests.

Written by the indexing model from the issue text.