When creating DISPUTE_OPEN message, node can put order into ERROR state when resolving moderator info

[placer14]

A bug was reported by a user where their order became "stuck" as a result of attempting to open a dispute. The order shows itself to be in a state of ERROR with the reason "could not resolve name" along with "LISTING", "ORDER", and "DISPUTE" signatures (suggesting the order has proceeded at least through creation of the dispute).

Processing of a dispute should not cause the order to become stuck in this case and should be reverted back to its state prior to being in "DISPUTE", particularly in this case where the ERRORing case is due to failed lookup of the vendor (which is a failure recoverable by retry). Investigation for how to apply this behavior needs to be done.

[placer14]

More information available in ZD ticket #11681