Ask for organization before finalizing the launch plan

[alichay]

Change Summary

What and Why: This solves two problems.

1. Users got annoyed that we picked Personal by default. This is totally understandable - we can pick reasonable default for everything else, but we have no information from which we can derive what organization the user wants. Asking directly will end up being faster and better UX here.
2. We want to support per-org launch features, such as waitlisted/beta addons, and this allows us to go into the launch web page with the exact knowledge of what org the app's going in. This simplifies the process on our side, and reduces surface area for bugs as we're introducing new addons and extensions.

How: We prompt for the org during the launch, just like we did with legacy launch.

Related to: discussion in #fly-launch, user feedback

---

Documentation

Not sure what the docs ramifications are of this, waiting to hear back about that :)

• [ ] Fresh Produce
• [ ] In superfly/docs, or asked for help from docs team
• [ ] n/a