chore: point to nixpkgs upgrade of status-go

[siddarthkay]

Summary

This PR points to status-go changes made in status-im/status-go#5848

Just want to ensure that nixpkgs upgrade in status-go does not break naything in status-desktop

cc @status-im/desktop-qa

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	66c6b13	#1	2024-09-20 09:44:04	~7 min	macos/aarch64	🍎dmg
✔️	66c6b13	#1	2024-09-20 09:44:04	~7 min	tests/nim	📄log
❌	66c6b13	#1	2024-09-20 09:48:49	~11 min	tests/ui	📄log
✔️	66c6b13	#1	2024-09-20 09:48:59	~11 min	macos/x86_64	🍎dmg
✔️	66c6b13	#1	2024-09-20 09:53:27	~16 min	linux-nix/x86_64	📦tgz
✔️	66c6b13	#1	2024-09-20 09:54:54	~17 min	linux/x86_64	📦tgz
✔️	66c6b13	#2	2024-09-20 10:15:24	~12 min	tests/ui	📄log

[status-im-auto]

✔️ status-desktop/prs/windows/x86_64/package/PR-16366#1 🔹 ~24 min 🔹 66c6b13 🔹 📦 windows/x86_64 package

[dlipicar]

@siddarthkay so it compiles and the squish tests passed. Do we need some dogfooding done? The changes to the nixpkgs seem to be mostly mobile-related, is there anything we can expect to go wrong for desktop?

[siddarthkay]

@dlipicar : the nixpkgs change impact how status-go is built and interfacing of status-go with status-desktop.
If squish test passes and @status-im/desktop-qa do no find any major issues during their smoke test then I can go ahead and merge the changes in status-go.