feat: handle auth flow natively

[pavanjoshi914]

Describe the changes you have made in this PR

one way we can eliminate identity api is to use completely native browser api so that we can support all the browsers including firefox for android

doesn't require any hacks or content script. just using tabs api and event listeners which works on all the browsers including android

[pavanjoshi914]

everything else is done only this is to create client. which requires a redirect url. not sure what to use as redirect url. new page in getalby.com?

[bumi]

Is there a way we can append the amount of accounts the user has to the URL?

[pavanjoshi914]

Is there a way we can append the amount of accounts the user has to the URL?

not sure about this. why we need that?

[bumi]

Is there a way we can append the amount of accounts the user has to the URL?

not sure about this. why we need that?

There are those reports that people struggling with adding another account when they are logged in because we don't prompt them.
So I thought maybe we auto authorize the first call but not when the user has multiple accounts already.

[pavanjoshi914]

we build auth url and add search-params in the following way in js-sdk

  url.search = buildQueryString({
      ...options,
      client_id,
      scope: scopes.join(" "),
      response_type: "code",
      redirect_uri: callback,
      code_challenge_method,
      code_challenge,
    });

I don't think we have any option to pass additional metadata such as a number of accounts. maybe we introduce such fields in options? or any separate field?

[reneaaron]

tACK

Created a follow-up-issue for improving the account connection in multi-account scenarios:

#2909