Should we rename siweAuthActionTypes to legacySiweAuthActionTypes and keyserverRegisterActionTypes to legacyKeyserverRegisterActionTypes?

Remove unnecessary code

Address review

In D11760#337835, @tomek wrote:

Is native also affected by this bug?

Make the code safer

Remove all actions but setAccessTokenActionType.
In the next diff I will move this reducer to native

Rebase

Remove unnecessary lines

I tested this and I was indeed able to login and register without these lines!

Rename

Show only one popup

A bit confused about the scenario you describe. How is the user able to log in after being logged out, if they can't auth with the authoritative keyserver? Doesn't the authoritative keyserver make the version check during auth?

Requesting review because now:

1. We can still see this modal more than once - for other keyservers. Is this that we want??
2. For the auth keyserver, the user is logged out. If they dismiss the modal, but ignore it and log in, they will be logged out and will NOT see the modal again. Is this ok or should I make logging in reset this state?

Memoize list of components, only display the alert once for each keyserver

Okay, this makes to me sense now

In D11643#334927, @tomek wrote:

Can't we simply reload the page when the client version is unsupported?

Now the modal looks like this:

Address review

It is also weird to me that we try to auth with the keyserver before identity login success. Maybe we should change that?

I worry that this may cause problems. Identity login and register clear data in case they are dispatched before logout success, so before user's data is cleared. This change makes it technically possible that the following will happen:

1. User A logs in with identity and the keyserver - gets a user cookie
2. User A logs out
3. User B logs in, and a login success is dispatched before logout success

Now user B has user A's keyserver cookie

Rebase

Please remove the unnecessary code in all places before landing. Other than that looks good

Rename function