[TX flow] Batch execute fixes

[usame-algan]

What it solves

Part of #2067

How this PR fixes it

• Hide the status widget for batch executions
• More visible warning message
• Close the modal when submitting the transaction

How to test it

1. Open a Safe with at least 2 fully signed transactions
2. Go to the Queue
3. Press Batch Execute
4. Observe an orange warning box at the bottom
5. Observe no Status widget
6. Switch to mobile view and observe no status widget toggle button
7. Execute transaction
8. Observe the modal closes

Screenshots

Checklist

• I've tested the branch on mobile 📱
• I've documented how it affects the analytics (if at all) 📊
• I've written a unit/e2e test for it (if applicable) 🧑‍💻

[github-actions]

Branch preview

⏳ Deploying a preview site...

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[iamacook]

All looks good but I'm not sure about entirely hiding the status widget. Perhaps we should just hide the irrelevant steps. What do you think?

[usame-algan]

All looks good but I'm not sure about entirely hiding the status widget. Perhaps we should just hide the irrelevant steps. What do you think?

I was also thinking about that but the only relevant step is "Execute" which we already tell the user in the subtitle by saying "Execute Batch".

[iamacook]

I was also thinking about that but the only relevant step is "Execute" which we already tell the user in the subtitle by saying "Execute Batch".

It seems odd without the widget as it doesn't "match" the flow. We could still show the "Execute" step. cc @liliiaorlenko (see screenshot in description)

[liliiaorlenko]

I was also thinking about that but the only relevant step is "Execute" which we already tell the user in the subtitle by saying "Execute Batch".

It seems odd without the widget as it doesn't "match" the flow. We could still show the "Execute" step. cc @liliiaorlenko (see screenshot in description)

yes I would still keep the execute step for sure, it makes sense in overall structure of transaction flow
maybe instead of "Execute batch" I would just use Batch

[usame-algan]

yes I would still keep the execute step for sure, it makes sense in overall structure of transaction flow maybe instead of "Execute batch" I would just use Batch

I've updated the status widget messages (see PR description).