Prevent Fendermint from crashing when a contract is reverted in top-down and bottom-up logic

[adlrocha]

Right now, there are several processes in the logic from top-down and bottom-up cross-net primitives (like the commitment of top-down finality or the bottom-up checkpoint creation and signature) that make the Fendermint process to crash when this shouldn't be the behavior. We can crash a validator as long as all validators crash consistently and the process is not consensus breaking.

For additional context, from @aakoshh comment here

For posterity: I see we are crashing if any of the 3 parts of the execution of top-down finality goes wrong.

I think that's not a bad way to go in the next two weeks, but I maintain that we should rethink our approach to execution to respect gas limits:

• by not voting on stuff over the limit Topdown finality proposal and execution fendermint#310 (comment)
• by deferring execution to later blocks with free gas capacity
  by putting all three aspects of finality into a single call that fails together, so can retry in a later block if it failed, rather than crash