chore: update the forgot-password modal verbiage

[seanstrom]

fixes #21849

Summary

• This PR attempts to update the verbiage for the "forgot password" modal that can appear from the login screen

Platforms

• Android
• iOS

Areas that may be impacted

Functional

• Forgot password modal

Steps to test

• Open Status
• Attempt to login to a profile using the wrong password
• Press on the "Forgot Password" link text

Screen Capture

https://github.com/user-attachments/assets/df96f020-4145-4ea7-9cea-1df702ed930f

status: ready

[status-im-auto]

Jenkins Builds

Click to see older builds (8)

:grey_question:	Commit	:hash:	Finished (UTC)	Duration	Platform	Result
:heavy_check_mark:	d13bcca8	#1	2025-04-03 14:19:17	~5 min	tests	:page_facing_up:log
:heavy_check_mark:	d13bcca8	#1	2025-04-03 14:20:15	~6 min	android-e2e	:robot:apk :calling:
:heavy_check_mark:	d13bcca8	#1	2025-04-03 14:22:33	~9 min	android	:robot:apk :calling:
:heavy_check_mark:	d13bcca8	#1	2025-04-03 14:25:01	~11 min	ios	:iphone:ipa :calling:
:heavy_check_mark:	1f1a1a69	#3	2025-05-19 13:42:26	~5 min	tests	:page_facing_up:log
:heavy_check_mark:	1f1a1a69	#3	2025-05-19 13:46:05	~8 min	android-e2e	:robot:apk :calling:
:heavy_check_mark:	1f1a1a69	#3	2025-05-19 13:46:38	~9 min	android	:robot:apk :calling:
:heavy_check_mark:	1f1a1a69	#3	2025-05-19 13:49:37	~12 min	ios	:iphone:ipa :calling:

:grey_question:	Commit	:hash:	Finished (UTC)	Duration	Platform	Result
:heavy_check_mark:	8be9533f	#4	2025-05-19 16:21:23	~4 min	tests	:page_facing_up:log
:heavy_check_mark:	8be9533f	#4	2025-05-19 16:24:19	~7 min	android	:robot:apk :calling:
:heavy_check_mark:	8be9533f	#4	2025-05-19 16:24:51	~8 min	android-e2e	:robot:apk :calling:
:heavy_check_mark:	8be9533f	#4	2025-05-19 16:28:54	~12 min	ios	:iphone:ipa :calling:
:heavy_check_mark:	b2f51855	#5	2025-05-20 06:02:25	~4 min	tests	:page_facing_up:log
:heavy_check_mark:	b2f51855	#5	2025-05-20 06:04:41	~7 min	android-e2e	:robot:apk :calling:
:heavy_check_mark:	b2f51855	#5	2025-05-20 06:06:37	~8 min	android	:robot:apk :calling:
:heavy_check_mark:	b2f51855	#5	2025-05-20 06:09:38	~11 min	ios	:iphone:ipa :calling:

[seanstrom]

@ilmotta yeah good points about helping the user understand that data recovery is not perfect. @xAlisher do you have any thoughts on this?

[xAlisher]

@ilmotta yeah good points about helping the user understand that data recovery is not perfect. @xAlisher do you have any thoughts on this?

Agreed, make sense to mention that some data might be lost.

[churik]

@seanstrom what's your take on this? may be let's try to finish it until release cut

[xAlisher]

https://www.figma.com/design/o4qG1bnFyuyFOvHQVGgeFY/Onboarding----Mobile?node-id=17007-28113&t=RGVhFIdzJ5IQqsAU-1

Proposal for update

cc @pedro-et

[churik]

@seanstrom let's do it like this? I'm totally agree on the proposal from @xAlisher , thanks!

[seanstrom]

Oki doki 🧑‍🌾

I've updated the verbiage with the latest proposal in this PR, here's how it looks:

[status-im-auto]

96% of end-end tests have passed

Total executed tests: 24
Failed tests: 1
Expected to fail tests: 0
Passed tests: 23

IDs of failed tests: 741841 

Failed tests (1)

Click to expand

Rerun failed tests

Class TestWalletCollectibles:

1. test_wallet_collectible_send_from_expanded_info_view, id: 741841

Device 1: Find `CollectibleItemElement` by `xpath`: `//*[@content-desc='collectible-list-item']//*[contains(@text,'Glitch Punks')]/../..` Device 1: Find `CollectibleItemElement` by `xpath`: `//*[@content-desc='collectible-list-item']//*[contains(@text,'Glitch Punks')]/../..` wallet/test_collectibles.py:159: in test_wallet_collectible_send_from_expanded_info_view self.wallet_view.get_collectible_element('Glitch Punks').scroll_and_click() ../views/base_element.py:209: in scroll_and_click self.scroll_to_element(direction=direction) ../views/base_element.py:204: in scroll_to_element raise NoSuchElementException( Device 1: CollectibleItemElement by xpath: `//*[@content-desc='collectible-list-item']//*[contains(@text,'Glitch Punks')]/../..` is not found on the screen; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#no-such-element-exception Device sessions Device 1: Steps, video, logs

Passed tests (23)

Click to expand

Class TestOneToOneChatMultipleSharedDevicesNewUi:

1. test_1_1_chat_send_image_save_and_share, id: 703391

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

2. test_1_1_chat_pin_messages, id: 702731

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

3. test_1_1_chat_message_reaction, id: 702730

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

Class TestWalletOneDevice:

1. test_wallet_swap_flow_mainnet, id: 741555

Device sessions Device 1: Steps, video, logs

2. test_wallet_balance_mainnet, id: 740490

Device sessions Device 1: Steps, video, logs

3. test_wallet_bridge_flow_mainnet, id: 741612

Device sessions Device 1: Steps, video, logs

4. test_wallet_send_flow_mainnet, id: 741554

Device sessions Device 1: Steps, video, logs

Class TestWalletCustomParamOneDevice:

1. test_send_snt_custom_tx_params, id: 742910

Device sessions Device 1: Steps, video, logs

Class TestProfileMultipleDevices:

1. test_profile_change_profile_photo, id: 741969

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

2. test_profile_change_username, id: 741968

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

Class TestGroupChatMultipleDeviceMergedNewUI:

1. test_group_chat_join_send_text_messages_push, id: 702807

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs Device 3: Steps, video, logs

Class TestCommunityOneDeviceMerged:

1. test_community_copy_and_paste_message_in_chat_input, id: 702742

Device sessions Device 1: Steps, video, logs

Class TestWalletCollectibles:

1. test_wallet_send_collectible, id: 741840

Device sessions Device 1: Steps, video, logs

2. test_wallet_collectibles_balance, id: 741839

Device sessions Device 1: Steps, video, logs

Class TestCommunityMultipleDeviceMerged:

1. test_community_message_delete, id: 702839

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

2. test_community_message_send_check_timestamps_sender_username, id: 702838

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

3. test_community_one_image_send_reply_set_reaction, id: 702859

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

4. test_community_message_edit, id: 702843

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

Class TestWalletMultipleDevice:

1. test_send_eth[Status Network Sepolia-0.0002], id: 727229

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

2. test_wallet_send_erc20_from_drawer[Sepolia-USD Coin-USDC (EVM)-2-0.01], id: 742016

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

3. test_wallet_send_erc20_from_drawer[Optimism Sepolia-USD Coin-USDC (EVM)-2-0.01], id: 727230

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

4. test_send_eth[Arbitrum Sepolia-0.0001], id: 742015

Device sessions Device 1: Steps, video, logs Device 2: Steps, video, logs

Class TestWalletOneDeviceTwo:

1. test_wallet_add_remove_regular_account, id: 727231

Device sessions Device 1: Steps, video, logs

[seanstrom]

@churik is it alright if we skip manual QA? I pre-emptively marked this as skippable, since it seemed like a small UI change, but what do you think?