fix: missing clusterID in node config

[richard-ramos]

Fixes #13355

The clusterID was not being sent when a change related to the node config was executed.
This issue is related to #12918 and should be fixed once proper endpoints for status-go node configuration changes are created

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	55087e6	#1	2024-01-30 19:56:33	~5 min	tests/nim	📄log
✔️	55087e6	#1	2024-01-30 19:57:44	~6 min	macos/aarch64	🍎dmg
✖️	55087e6	#1	2024-01-30 20:01:36	~10 min	tests/e2e	📄log
✔️	55087e6	#1	2024-01-30 20:01:44	~10 min	tests/ui	📄log
✔️	55087e6	#1	2024-01-30 20:03:07	~12 min	macos/x86_64	🍎dmg
✔️	55087e6	#1	2024-01-30 20:07:40	~16 min	linux/x86_64	📦tgz
✔️	55087e6	#1	2024-01-30 20:23:36	~32 min	windows/x86_64	💿exe
✖️	55087e6	#2	2024-01-30 20:38:42	~33 min	tests/e2e	📄log
✖️	55087e6	#3	2024-02-05 12:32:09	~8 min	tests/e2e	📄log
✔️	55087e6	#4	2024-02-05 13:06:28	~30 min	tests/e2e	📄log

[igor-sirotin]

hmm, I thought this thing is fleet-dependant 🤔

[richard-ramos]

Yes; the fleet details are still stored in the node config, and for some operations in desktop we modify the node config directly - i.e., switching the log level -, so if the node config object in desktop, is missing the clusterID, when we sent the new node config to status-go, it will store the clusterID with a 0, since it will use the default value, instead of using the correct clusterID which was stored in the node config before changing the log level.