If publish fails, retry on a different catalyst

[nearnshaw]

If there's an issue with a catalyst, the publishing fails in a very unfriendly way

Today creators use the command line to force pointing to a specific catalyst, which to most users is extremely outside their confort zone npm run deploy -- --target [peer-ec1.decentraland.org](http://peer-ec1.decentraland.org/)

We don't control many of the catalysts, and it's very common for one of them to have problems, we've been in this situation countless times.

When We need the Creator Hub to retry automatically with different catalysts until one works. The user doesn't need to find out that any of this is going on, it should be invisible to them.

We can take inspiration from this workaround done on the Badges feature, that retries with different catalysts if an operation fails:
https://github.com/decentraland/badges/blob/main/processor/src/adapters/badge-context.ts#L50-L65