[Feature] Handle OAuth flow differently when users try to connect a second account

### Feature description

Currently OAuth flows for Alby users are automatically approved. That makes it cumbersome for users to connect their wallet in multiple-account scenarios, since they have to first logout on getalby.com.

### Describe the solution

There are 2 possible solutions:
- Disable to auto-approval of the extension
- Pass a parameter to the OAuth flow and skip auto-approval (to give users a chance to logout during the flow)

### Describe alternatives

_No response_

### Additional context

_No response_

### Are you working on this?

None

Start by tracing the extension's OAuth approval flow and how it handles connecting an account. Compare the two proposed approaches and confirm the intended behavior for a second account; done means users can reach the needed logout step without first logging out on getalby.com.

Written by the indexing model from the issue text.