chore: send one msg per tx if batch of msgs fails

[RafilxTenfen]

Currently, the covenant emulator sends multiple msgs in the same transaction, but if any of these msgs fails, the entire transaction is reverted, so the idea is to try to batch it all first, if it fails it sends multiple transactions each one with a single message inside of it

A good portion of the code added was a copy/adapt from https://github.com/babylonlabs-io/babylon/blob/cd0bbcd98be5e4dda081f7330140cf9dbee4c94d/client/client/tx.go#L76

and it could be solved by adding an option in the Babylon client to send multiple transactions in the same block each one with a single TX inside of it

Modified e2e run in CI, to initiate one test in each machine, since each StartManagerWithFinalityProvider initiates a few processes and one test might affect the other

As the fix is a secondary option it becomes hard to e2e test, so I disabled the batch msgs in a single tx to test. CI run sending one msg per tx https://github.com/babylonlabs-io/covenant-emulator/actions/runs/12890756219/job/35941075950 and https://github.com/babylonlabs-io/covenant-emulator/actions/runs/12892910683/job/35948185923

Closes: #87

[Lazar955]

actually this whole file should be deleted, I just removed it from relayer code I copied over (those where the annoying logs)

[RafilxTenfen]

are you recomending to remove these log calls?

[Lazar955]

Ah, mb must have missed it, just got triggered as that's the code from the relayer repo. We can leave the logs in, but I think for us more important are the metrics in general

[Lazar955]

Ah somehow I missed this file, could we modify our client code in Babylon repo to add this. As it's pretty much a duplicate now of 429. It might be better than adding a bunch of same code here. Would make sense to do it after 429 is merged.
Unless this is urgent and we need to get it in now

[RafilxTenfen]

@KonradStaniec not sure if this is urgent to be in the next release