[ SW-467 ] fix(threshold-info): Display right info in the change threshold confirmation screen

[clovisdasilvaneto]

What it solves

Confirm threshold screen is showing 0 of (n) when user comes from the transaction list.

How this PR fixes it

Before we were grabbing the threshold information from the changeThreshold screen flow, but this information is not available when user comes from the transactions list (for eg, in order to confirm a change threshold transaction)

How to test it

• Change the threshold of your account
• sign but do not execute it
• go to the transaction list and try to confirm or execute it from there.
• The amount of required signers now should be working as expected instead of showing "0 out (n)"

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

✅ Deploy successful!

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

Storybook:
https://fix_threshold_in_confirmation_view--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. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	74.09% (+0.01% 🔼)	13904/18767
🔴	Branches	52.72% (-0% 🔻)	3427/6500
🔴	Functions	57.92%	2029/3503
🟡	Lines	75.76% (+0% 🔼)	12633/16675

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / index.tsx	100%	40% (-60% 🔻)	100%	100%

Test suite run success

1593 tests passing in 215 suites.

Report generated by 🧪jest coverage report action from 98af511

[notion-workspace]

🔧 Dev: 0 of N confirmation in case of changing policy

[francovenica]

Looks good to me.

A before/after screenshots: