Better error reporting in the TUI when transaction posting fails on chain

[pgrange]

Problem: When a tx submission fails it's not clear why because the error messages are obscure/cryptic/not visible
We cannot remember exactly what the problem was initially so we need to make sure we clarify the problem

Goal: We want the node to provide better error reporting when a L1 transaction posting fails (not when it's not observed) immediately, possibly giving a human-understandable message :)

• Reproduce manually issue on a working head, possible steps:
  • ensure the user does not have enough fund to post init tx (or will lead to a lower than minimal UTxO)
  • start a head in TUI
  • post init
  • see it fail -> is it understandable/visible/actionable?

[pgrange]

We should have given more details to this story.

We should try to open our head again to see if we stumble upon the issue again

See #366 for more context to this issue

[pgrange]

These are the big 5 potential errors which output we can improve:

data ErrCoverFee
  = ErrNoAvailableUTxO
  | ErrNotEnoughFunds Text
  | ErrUnknownInput Text
  | ErrNoPaymentUTxOFound Text
  | ErrScriptExecutionFailed Text
  | ErrCostEstimation Text

We should focus on errors for which a user can do something about so that we help him fix the situation and let the other errors as they are for now:

• ErrNotEnoughFunds
• ErrNoPaymentUTxOFound
• ErrNoAvailableUTxO

Out of scope for now ("more details in the logs"):

• ErrUnknownInput
• ErrCostEstimation