Don't fetch txDetails for Batch Execute

[usame-algan]

This issue is currently blocked by #2011

What is the feature about

We fetch txDetails for every transaction that is part of the batch when using Batch Execute in the UI. This is because we need the dataDecoded in order to display what each transaction does (method name, parameters). Once Human-readable transactions are implemented we will have access to that information without having to fetch txDetails.

The list of requirements

• Remove txDetails requests from Batch Execute
• Use txInfo.humanDescription or txInfo.richInfo instead

[usame-algan]

This would also address 5afe/safe-support#269

Discussion on Slack

[iamacook]

It looks like we will need to fetch them for execution as we extract the arguments of a transaction from the txDetails.

[usame-algan]

It looks like we will need to fetch them for execution as we extract the arguments of a transaction from the txDetails.

True, that means we can't get rid of the fetch calls and need to tackle this on the CGW. I will close this issue and bring it up on Slack.