Test: detect duplicated signer in safe creation

[francovenica]

What it solves

Ticket #3427 fixed an issue of duplicated owner in safe creation in a specific scenario. This is an e2e-test that detects if that issue happens again

How this PR fixes it

Adds an address of the currently connected owner to the LS (like if it was added to the address book)
Uses the autocomplete feature in the safe creation owners' step to selecte the address added to the LS
Makes sure the "Duplicated signer" error shows up for that scenario

How to test it

Run the test "Verify duplicated signer error using the autocomplete feature" in the "create_test_simple" file. It should run fine
No other tests should be affected, so they all should run fine as well

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!

https://e2e_duplicated_signers--walletweb.review-wallet-web.5afe.dev/home?safe=eth:0xA77DE01e157f9f57C7c4A326eeE9C4874D0598b6

[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}

[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	79.38%	11122/14011
🔴	Branches	58.4%	2610/4469
🟡	Functions	66.1%	1794/2714
🟢	Lines	80.64%	10018/12423

Test suite run success

1411 tests passing in 195 suites.

Report generated by 🧪jest coverage report action from ec72384