fix(mu): message loss due to messages going directly to Arweave

[VinceJuliano]

Background

It has been an ongoing challenge for the MU to detect whether a message is going to a process or directly to Arweave because it is sent to a wallet. There are still messages going incorrectly to Arweave for example W1R6Gq8Y11AS2_GuS96e0cRKc95r7qHB9wE6iQ4FJUM. The main cause of this is that it is difficuilt to make the isWallet function reliable.

Solution

Find some way to determine reliably if an id is a wallet, or, try to send it to the su for the given id, and if it isnt present on that su, send it to arweave.