feat(tx-builder-mode): share dark mode information with safe apps

[clovisdasilvaneto]

What it solves

Resolves safe-global/safe-react-apps#824

How this PR fixes it

It adds the getCurrentTheme method into the app communicator in order to share the darkMode information with the transaction builder or any other safe app.

How to test it

• Take the transaction builder dark mode deployed PR link and add it on your safe
• Open the custom tx-builder app which you just added
• change the dark mode toggle on the sidebar
• the transaction builder theme should change according to safe wallet theme

Screenshots

txbuilder.webm

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

Storybook:
https://feat_tx_builder_dark_mode--walletweb.review.5afe.dev/storybook/

[clovisdasilvaneto]

I'll be sending the PR soon to the safe-react-apps repository

[github-actions]

📦 Next.js Bundle Analysis for safe-wallet-web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Two Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/apps/open	53.19 KB (🟡 +83 B)	1014.36 KB
/home	58.2 KB (🟡 +83 B)	1019.37 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	78.12% (+3.69% 🔼)	12011/15375
🔴	Branches	58.22% (+5.39% 🔼)	3091/5309
🟡	Functions	65.12% (+6.5% 🔼)	1891/2904
🟡	Lines	79.66% (+3.52% 🔼)	10842/13610

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / pk-popup-store.ts	80% (-10% 🔻)	50%	0%	88.89%
🟢	... / stake.ts	75% (-25% 🔻)	100%	100%	100%
🟢	... / useLoadChains.ts	93.75% (+1.44% 🔼)	66.67% (-33.33% 🔻)	100%	100%

Test suite run success

1498 tests passing in 203 suites.

Report generated by 🧪jest coverage report action from f19cfae