fix: Handle special characters for prefix in address input

[usame-algan]

What it solves

Noticed that the AddressInput unit test randomly fails sometimes. This happens when faker generates a shortName with a hyphen or other special characters in it so I adjusted our cleanup function to handle such characters.

How this PR fixes it

• Updates cleanInputValue to not only handle a-z0-9 characters in the prefix but any character that is not a :
• Adds unit tests for cleanInputValue

How to test it

1. Create a send transaction
2. Input test-prefix:<some address> into the recipient field
3. Observe that the value is not changed
4. Input a real chain prefix like eth:<some address>
5. Observe that it is the same behaviour as previously

Screenshots

On prod when typing test-hyphen:<some address>

With the change when typing test-hyphen:<some address>

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

Storybook:
https://fix_address_input_test--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	78.09% (-0% 🔻)	11999/15365
🔴	Branches	58.21% (+0.04% 🔼)	3084/5298
🟡	Functions	65.09%	1889/2902
🟡	Lines	79.63% (-0% 🔻)	10830/13600

Test suite run success

1497 tests passing in 203 suites.

Report generated by 🧪jest coverage report action from 2a65e52

[francovenica]

Never thought about entering a network with a special character. LGTM