✨ Add Entrypoint That Sends Funds To a Recover Addr Upon Failure

[brimigs]

Since there are multiple contracts and entry points involved in the overall end to end transactions of the skip api, if an error occurs midway through the funds get "stuck" because the error will only revert to the beginning of the specific message that failed, not the entire transaction.

IMO the best way to handle this is by implementing sub-messages and replies, allowing us to handle the result of executing another contract.

Wrapping each returned message with a SubMsg, then handling the reply.id in the reply entry point gives us a way to properly handle all msgs that error. If an error is sent back to the contract, the reply message will return the tokens to the recovery address.

[NotJeremyLiu]

Overall this is great!

I left some comments/suggestions on some places where I believe changes need to be made.

After those changes, would love one more run through to try and standardize some of the formatting / structure with the rest of the contract, the place I noticed this was that you defined the logic of AxelarSwapAndAction in contract.rs, whereas the rest of the contract defines the function that handles the logic in execute.rs.

I also noticed some unnecessary clones which when I run make clippy locally they're flagged but CI did not catch them so something in our CI is funky (I'd expect clippy CI to fail here), I'll look into CI later but if you could fix the clippy warnings running locally that would be great!

[NotJeremyLiu]

lgtm, let's start recovering!