Enable re execution of failed one way messages

[AntonAndell]

Currently when a one way message fails it is simply thrown away, to allow more efficient use of many cross chain protocols we need to guarantee the execution of these messages, so no data is lost.

[AntonAndell]

The issue with this is that there is a potential for many non executable messages are stored. If used with a protocol that increases cost per storage unit we might need a pruning functionality. But no such protocol is planned for integration that i know off.

[AntonAndell]

Another issue is that payloads can be stored that should be removed.
Example a borrow or a bid that was supposed to only be relevant at a time and not in the future. Having it stored indefinitely can cause unexpected attack vectors to current xCall dapp designs. So lets hold off on a change like this.