Rework Invite Code Experience

[bfollington]

Fixes #715
Fixes #697
Fixes #738
Fixes #763
Fixes #737

Demo

I can't record a fresh demo right now since the cluster is down, I recommend playtesting the app. But here's a slightly stale video of the new settings layout. All the gateway settings are together now, it's maybe a bit confronting for users but they have full control to pick-up the process at any point it failed.

Screen_Recording_2023-06-28_at_1.44.19_pm.mov

First Run

Settings

Rework the invite code flow to ensure the code is actually valid. See screenshots in comments throughout.

• Add latest graphic here + in docs
• Attach videos & screenshots to aid review
• Introduce tests for first run step submission/validation
• Test new FormField functionality
• Tweak invite redemption failure message
• Rework isValid abstraction
• .pushStep for FirstRun

[gordonbrander]

The graphic in the issue is great.

We could consider creating a docs dir at the top level and dropping it in.

[gordonbrander]

A few comments. Otherwise, LGTM!

[gordonbrander]

We should allow changing the invite code, at least in the settings, and probably in the FRE? If you put in the wrong invite code in this PR, there would be no recovery path.

I recently attempted to re-use invite code during a playtest, with a predictable failure. However, without a way to write in a new invite code, I believe I would have been bricked #738

[bfollington]

Based on feedback here and the work we're doing in https://github.com/subconsciousnetwork/subconscious-cloud/issues/6 I think we should rethink the overall flow here a little.

We can address #737 and #738 easily once https://github.com/subconsciousnetwork/subconscious-cloud/issues/6 lands.

[bfollington]

Doing some modelling to explore how things would work after https://github.com/subconsciousnetwork/subconscious-cloud/issues/6 lands.

@gordonbrander let me know what you think, especially about my callout here RE: trying to redeem a code multiple times.

https://www.figma.com/file/jLgkHEJgiXICUK4y3UmcU6/Subconscious-Whiteboard?type=whiteboard&node-id=27-1056&t=KZxLhKs7zUCCntdO-4

[jsantell]

Clarifying the current planned changes in the redemption, mostly compatible with the flow above:

• Invite codes are bound to the provided sphere on redemption.
• Provisioning with the same invite code/sphere pair is idempotent.
• Provisioning request can fail via an internal error, or if invite code is invalid (not legit, or claimed by another sphere, we do not specify). The error "type" and its "error" message are available in JSON for non-200 responses.
• The provisioning request returns gateway ID regardless of state (whether provisioned or provisioning). Status must be queried after to handle whether pending/ready.
• If provisioning task fails, the provisioning request can be retried.

[bfollington]

Clarifying the current planned changes in the redemption, mostly compatible with the flow above:

• Invite codes are bound to the provided sphere on redemption.
• Provisioning with the same invite code/sphere pair is idempotent.
• Provisioning request can fail via an internal error, or if invite code is invalid (not legit, or claimed by another sphere, we do not specify). The error "type" and its "error" message are available in JSON for non-200 responses.
• The provisioning request returns gateway ID regardless of state (whether provisioned or provisioning). Status must be queried after to handle whether pending/ready.
• If provisioning task fails, the provisioning request can be retried.

Amazing! Thanks @jsantell, I had a quick read over https://github.com/subconsciousnetwork/subconscious-cloud/pull/7/files#diff-e1e65eeceb23dd47013779351844a41a2b781e987c92db2bb0d4fa60d51703b9 and updated the diagram with a few more details.

[gordonbrander]

LGTM. Haven't test-driven, but nothing looks unusual or out-of-place to me. Good improvements!