NetworkKeys: note potential delay after cycling keys

[marcusmiguel]

Resolves #1104

Displaying a waitMessage not only after the user has breached but also after a simple reset. Additionally, the content of the waitMessage has been updated to provide more accurate and useful information.

[shawntobin]

Looks good

[pkova]

@marcusmiguel the very first time someone accepts an L2 invite we have the following hack in place:

When they get their networking keys, they actually get two keys concatenated into one:

1. The current networking key (belongs to the star).

2. The key that is self-sovereign after the roller batch fires.

We do this so that people don't have to wait for the roller and are able to boot immediately. This does not apply on subsequent rekeys, so we need to make sure this message is only visible on subsequent rekeys and not the initial activation flow.

[pkova]

On second thought I think this is fine. The activation flow is completely self-contained and does not enter Bridge proper at all. This screen is not going to be visible for first-time L2 activators.