feat: lnurl-auth onboarding

[pavanjoshi914]

lnurl auth onboarding shifted in enable screen

Link this PR to an issue [optional]

Fixes #2713

Type of change

(Remove other not matching type)

• feat: New feature (non-breaking change which adds functionality)

Screenshots of the changes [optional]

Add screenshots to make your changes easier to understand. You can also add a video here.

2023-09-15.10-41-24.mp4

Checklist

• Self-review of changed code
• Manual testing
• Added automated tests where applicable
• Update Docs & Guides
• For UI-related changes
• Darkmode
• Responsive layout

[rolznz]

Some issues on this dialog:

• Copy is not so good in this case. We can now be more specific (we require a different onboarding component for LNURL auth?). Maybe we could say "A master key is required for Lightning Login"
• Buttons should be bottom aligned

[pavanjoshi914]

// allowance is set, keys available for alby connector - no prompt direct login
// allowance is set keys not available for alby connector - open onboard
// allowance not set, keys available for ably connector - open login prompt
// allowance is not set, keys are not available for alby connector - open onboard
// allowance is  connector is different:  direct login
// allowance is not set, connector is different: open login prompt

[rolznz]

@pavanjoshi914 when I disable login from the allowance, refresh the page and login I get an error:

[rolznz]

@pavanjoshi914 when I disable login from the allowance, refresh the page and login I get an error:

It also happens when I am using an LND connector, when I disconnect the site (completely remove the allowance), refresh, and then try to login again (on https://webln.twentyuno.net/login)

[pavanjoshi914]

@pavanjoshi914 when I disable login from the allowance, refresh the page and login I get an error:

It also happens when I am using an LND connector, when I disconnect the site (completely remove the allowance), refresh, and then try to login again (on webln.twentyuno.net/login)

Fixed in new commits

that happened because I was just calling the authPrompt, and not returning the response given by the authPrompt call. we need to return response back to content script else it will get a response as undefined.

[rolznz]

tACK

[pavanjoshi914]

instead of depending on connector type, now we depend on user wish to use mnemonic or not. the behaviour is::

for other connectors
a. if they have master key, and toggle enabled use master key for login
b. if they don't have key or toggle is disabled. use sign message which works by default for other connectors

2. for alby connector
   if no master key . show onboarding
   if master key and toggle is off - fallback to sign message method, which will then not work which is expected