fix: Set pending state for batched transactions

[usame-algan]

What it solves

Resolves RC issue

Fixes a regression introduced in #4158

How this PR fixes it

• Sets nonce when emitting tx events from the batch execution

How to test it

1. Queue and sign at least 2 transactions
2. Bulk execute them
3. Observe the Execute button changing to a processing state

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

✅ Deploy successful!

Website:
https://fix_batch_pending_state--walletweb.review.5afe.dev/home?safe=eth:0xA77DE01e157f9f57C7c4A326eeE9C4874D0598b6

Storybook:
https://fix_batch_pending_state--walletweb.review.5afe.dev/storybook/

[github-actions]

📦 Next.js Bundle Analysis for safe-wallet-web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page	Size (compressed)
global	954.83 KB (🟢 -6.28 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Six Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/apps	50.01 KB (🟡 +1.61 KB)	1004.83 KB
/apps/custom	41.64 KB (🟡 +1.61 KB)	996.46 KB
/apps/open	54.7 KB (🟡 +1.61 KB)	1009.53 KB
/home	59.72 KB (🟡 +1.61 KB)	1014.55 KB
/settings/notifications	27.03 KB (🟡 +2 B)	981.85 KB
/settings/safe-apps	25.53 KB (🟡 +1.61 KB)	980.35 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	78.1% (+0.01% 🔼)	12001/15366
🔴	Branches	58.19% (+0.02% 🔼)	3085/5302
🟡	Functions	65.09%	1889/2902
🟡	Lines	79.64% (+0.01% 🔼)	10832/13601

Test suite run success

1484 tests passing in 203 suites.

Report generated by 🧪jest coverage report action from b0f6b53

[compojoom]

Great! Tested it and it works!