submitTxToNodeLocal leaky exception

[Jimbo4350]

Description
When using Cardano.Api.submitTxToNodeLocal during defensive mempool operation, a BearerClosed network exception can bubble up to the caller instead of being caught and returned as a SubmitFail{} result. This violates the API's contract and breaks client error handling.

Observed Exception
BearerClosed "<socket: 12> closed when reading data, waiting on next header True"

[carbolymer]

This violates the API's contract and breaks client error handling.

submitTxToNodeLocal :: MonadIO m => LocalNodeConnectInfo -> TxInMode -> m (SubmitResult TxValidationErrorInCardanoMode) 

this function is running in MonadIO so it will be always possible to throw an exception in IO. The proper solution here is for function users to always wrap this function in try / catch.

I think the question here is whether we should consider BearerClosed ... error a recoverable one and wrap it in SubmitFail.