Made SendKeyForAccountFlow return the created key too.

[xavierlepretre]

Added tests too.

Unlike ProvideKeyFlow, SendKeyForAccountFlow does not return the created key. This pull request fixes that.

The use case is where both ends of the flow come to agreement about which key to use.

• the initiator has an abstract function, which is overridden with a key creation flow request.
• the responder has an abstract function, which is overridden with a key creation flow

Because both ends need to know the key created, it was not possible to use RequestKeyForAccountFlow, and instead RequestKeyFlow was used.

[roastario]

when you throw an exception on the responder flow, it is quite a bit harder to figure out what the actual issue is due to the way that errors are masked from initiators.

@xavierlepretre could you restore the existing FOUND/NOT_FOUND response, and then looks good to me.

[xavierlepretre]

@roastario

1. I thought that with a FlowException thrown in the responder, it was propagated back to the initiator, which is waiting for a reply.
2. If I reinstate the found / not found state, the responder will have to return a PublicKey? while the initiator can return a PublicKey. Unless the responder sends back "not found" and then throws (not sure about the implications of this double action). Is any ok?