Align deployment of Safe to be of same version as Safe UI-deployed and having fallback handler attached

[mudrila]

Description

This PR swaps all the GnosisSafe usages to GnosisSafeL2 and adds fallbackHandler to the create Safe flow, right into setup function call.

Notes

Issue

Closes #1361

Testing

1. Deploy brand new Safe via Fractal
2. Create new Safe via Safe UI, go to Safe's Settings page
3. Go to Safe UI and find Fractal-created Safe, go to Safe's Settings page
4. Compare Safe created via Fractal and Safe created via Safe UI - their version should be exactly the same (1.3.0+L2) and attached Fallback Handler (could be found under "Modules" tab) also should be exactly the same. See screenshots below for references on how it should look like

Screenshots (if applicable)

[netlify]

✅ Deploy Preview for fractal-framework-interface-dev ready!

Name	Link
🔨 Latest commit	dffbb6a
🔍 Latest deploy log	https://app.netlify.com/sites/fractal-framework-interface-dev/deploys/65dcf0e5a95b7500083c1d37
😎 Deploy Preview	https://deploy-preview-1375--fractal-framework-interface-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Da-Colon]

Surprised we still have to rely on the typechain files for these. But tested and it indeed works. I see that the Contract+L2 is correctly displayed in the settings and the CompatibilityFallbackHandler has been set up as a module.

[adamgall]

Whenever using the safe-deployments package to get singleton addresses, the filter simply confirms that the contract has been deployed on the given network.

It's still up to the caller to dig into the networkAddresses object of the result to find the official address for a given chain, do not rely on the defaultAddress!

This applies to the new CompatibilityFallbackHandler code (which seems good for Sepolia and Polygon, but might as well do it for Mainnet too), as well as the actual Master Safe Singleton deployment address as well (for ALL THREE networks).

[adamgall]

Surprised we still have to rely on the typechain files for these. But tested and it indeed works. I see that the Contract+L2 is correctly displayed in the settings and the CompatibilityFallbackHandler has been set up as a module.

Pretty lucky that we had those GnosisSafeL2 types in that usul folder, huh! It looks like the only reason we had those types in the project, before, this PR, was to get the Multisend typing.

[adamgall]

LGTM!