fix: upgrade transactions for 1.0.0 Safes

[schmanu]

What it solves

Upgrade transactions for 1.0.0 Safes included an empty transaction instead of the setFallbackHandler call.

How this PR fixes it

Uses the Safe contract interface of the upgraded Safe's version instead of the current Safe's version.
This is correct as we first upgrade and change the masterCopy and then set the FallbackHandler.

How to test it

• Create a 1.0.0 Safe on e.g. Gnosis Chain
• Upgrade it to 1.4.1 through our interface

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_upgrade_1_0_0_safes--walletweb.review.5afe.dev/home?safe=eth:0xA77DE01e157f9f57C7c4A326eeE9C4874D0598b6

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

[notion-workspace]

Safe 1.0.0 upgrade transactions are broken

[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.07% (-0% 🔻)	13902/18768
🔴	Branches	52.69% (-0.02% 🔻)	3423/6496
🔴	Functions	57.92%	2029/3503
🟡	Lines	75.75% (-0% 🔻)	12631/16675

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / safeUpdateParams.ts	95.24% (-4.76% 🔻)	0% (-100% 🔻)	100%	95% (-5% 🔻)

Test suite run success

1593 tests passing in 215 suites.

Report generated by 🧪jest coverage report action from 045c7d5

[liliya-soroka]

Verified:
checked mastercopies:
1.1.1
1.0.0