refactor: onboarding after install

[fbwoolf]

Try out this version of the Stacks Wallet - download extension builds.

This PR changes the onboarding flow so that now after install the user is directed back to their app tab and it reloads the page so the extension can be detected as installed.

Issues:
hirosystems/connect#144
hirosystems/connect#98

Testing:

1. Point at the alpha release changes to connect linked in the PR above.
2. Run the test-app
3. Load the unpacked version into Chrome
4. Going thru onboarding in the full-page wallet
5. After you set your password, the ext should automatically redirect you back to the app tab
6. Click on Sign up again
7. Choose an account
8. Done

I think ultimately the goal is to extract out the concept of the Sign up button in the test-app and make it available via the connect library (@jasperjansz new designs for onboarding), but this is a good first step.

cc/ @aulneau @kyranjamie @fbwoolf

[changeset-bot]

🦋 Changeset detected

Latest commit: ce7dfa0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@stacks/wallet-web	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/blockstack/stacks-wallet-web/GHHfpfydpfbKy2ZTLBe4VFjJwSek
✅ Preview: https://stacks-wallet-web-git-refactor-onboarding-aft-b52bab-blockstack.vercel.app

[kyranjamie]

Good work @fbwoolf—I've added some comments wrt readability and keeping with the patterns being used currently.

[kyranjamie]

Can you explain why this is needed?

[fbwoolf]

I had to change it to this to query all tabs. I think activeTab only allows you to have access to the active tab.

[fbwoolf]

@kyranjamie one thing I noticed a little weird in testing this with the test-app is that when back at that app page the wallet is loaded but I still have to select an account before it moves past the sign up page. It seems like it should always just default to select the first indexed account to move an app past auth?

[aulneau]

It seems like it should always just default to select the first indexed account to move an app past auth?

I think for first time registrations this makes a lot of sense

[fbwoolf]

It seems like it should always just default to select the first indexed account to move an app past auth?

I think for first time registrations this makes a lot of sense

Been working on a solution for this, do either of you know why logging window to the console shows StacksProvider but if I console.log window.StacksProvider it is undefined (in the test-app)? Must be something with it being injected via the inpage script?

[kyranjamie]

Bizarre. Does window === window // true? They should resolve to the same place.

[fbwoolf]

Going to close this PR, it is really outdated. Will be discussed further here: #1808