Feat/deep link unfurl 16345

[Cuteivist]

Note: Already reviewed in #16541 (merge by mistake)

Task #16412

User stories: https://www.notion.so/Transaction-deep-link-10d8f96fb65c803c85fed5f4440ad439

Status-go : status-im/status-go#5958

What does the PR do

• Added unfurling of transaction deep links
• Added preview mini card for transaction preview (chat input)
• Added chat preview card for transaction preview
• Updated storybook

NOTE that this feature is behind feature flag. The design is not finished yet.

Affected areas

Chat

Architecture compliance

• I am familiar with the application architecture and agreed good practices.
  My PR is consistent with this document: Status Desktop Architecture Guide

Screenshot of functionality (including design for comparison)

unfurling.mov

Impact on end user

What is the impact of these changes on the end user (before/after behaviour)

How to test

• How should one proceed with testing this PR.

SET FLAG_TRANSACTION_DEEP_LINK_ENABLED env variable to 1 before running Status

• What kind of user flows should be checked?

Send / Bridge / Swap share button pasting

Risk

Described potential risks and worst case scenarios.

Tick one:

• Low risk: 2 devs MUST perform testing as specified above and attach their results as comments to this PR before merging.
• High risk: QA team MUST perform additional testing in the specified affected areas before merging.

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	fa9984c	#1	2024-10-21 10:39:28	~6 min	macos/aarch64	🍎dmg
✔️	fa9984c	#1	2024-10-21 10:40:09	~7 min	tests/nim	📄log
✔️	fa9984c	#1	2024-10-21 10:45:09	~12 min	tests/ui	📄log
✔️	fa9984c	#1	2024-10-21 10:51:21	~18 min	linux-nix/x86_64	📦tgz
✔️	fa9984c	#1	2024-10-21 10:52:31	~19 min	linux/x86_64	📦tgz
✔️	fa9984c	#1	2024-10-21 10:52:38	~19 min	macos/x86_64	🍎dmg
✔️	fa9984c	#1	2024-10-21 11:00:19	~27 min	windows/x86_64	💿exe

[alexjba]

The code LGTM! 👍 Although some tests would be nice here. Maybe a simple smoke test for the squish E2E would be a good option? To test the URL generation, the presence of the preview card and opening the card.

Have you considered/tested mixing sender/receiver testnet flag?
E.g. Sender shares transaction url with testnet on. Receiver clicks the card with main net enabled (and vice versa).

[Cuteivist]

The code LGTM! 👍 Although some tests would be nice here. Maybe a simple smoke test for the squish E2E would be a good option? To test the URL generation, the presence of the preview card and opening the card.

Have you considered/tested mixing sender/receiver testnet flag? E.g. Sender shares transaction url with testnet on. Receiver clicks the card with main net enabled (and vice versa).

That might be the the case. For example someone might send link to STT (testnet) tx, but other user might open it on mainnet. The result of that will be no asset selected.

I will ask design on that case, as they might not be aware of that.