Resubmit action for operations - such as data exchange send #74
Description
Operations can fail, such as a private send, or a pin against a blockchain - even with resilient plugins.
At the point the operation is initiated it's locked in a bunch of locally sequenced messages into a batch, and in the case of a pinned private transfer, those messages could arrive over the blockchain and not over private messaging (or vs. versa).
This means that the topics of messages in that batch are stuck - they can't proceed past the blockage.
The operation that failed needs to be re-initiated once the underlying failure is resolved.
So we need to prove a REST API to attempt re-submission, and the UI will be able to add a simple 'retry' for failed operations.
All the data should be available to re-submit, and the processing surrounding the operations is all designed to be idempotent.
So double-sending, or double-pinning, does not actually break the model.
The first sequence to be confirmed on the blockchain wins.