Feat/request payment modal 16736

[Cuteivist]

Closes #16736

What does the PR do

• Added feature flag for Request Payment. Disabled until whole feature is finished
• Added Request payment modal
• Added menu for message commands (now featuring add image and add request payment). Request payment is disabled for testnet to prevent corner cases or issues.
• Added RequestPaymentStore to easily pass required models and stores to modal
• Updated storybook

Affected areas

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)

• I've checked the design and this PR matches it

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.
  Enable request payment feature flag, go to any chat on mainnet.
• What kind of user flows should be checked?

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
❌	cfc1b4c	#1	2024-11-11 14:26:13	~7 min	macos/aarch64	📄log
✖️	cfc1b4c	#1	2024-11-11 14:26:28	~7 min	tests/nim	📄log
❌	cfc1b4c	#1	2024-11-11 14:29:04	~9 min	tests/ui	📄log
❌	cfc1b4c	#1	2024-11-11 14:29:38	~10 min	linux-nix/x86_64	📄log
❌	cfc1b4c	#1	2024-11-11 14:30:47	~11 min	macos/x86_64	📄log
❌	cfc1b4c	#1	2024-11-11 14:30:48	~11 min	linux/x86_64	📄log
❌	cfc1b4c	#1	2024-11-11 14:33:09	~13 min	windows/x86_64	📄log

[caybro]

LGTM in general, apart from the vertical (mis)alignment between the amount and the token selector when looking at the screenshot :)

[caybro]

Are we fine with loss of precision here? 🤔