fix: Allow state updates in Snaps interfaces to state values that are falsy

[FrederikBolding]

Description

Fixes a problem where state updates to Snaps interfaces would be ignored if the value was falsy, e.g. empty string.

Screenshots/Recordings

Before

2024-09-30.12-37-41.mp4

After

2024-09-30.12-39-14.mp4

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[metamaskbot]

Builds ready [2ab2f28]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1866 ± 171 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	333	3136	1759	476	229
		domContentLoaded	1447	3117	1834	353	170
		load	1455	3151	1866	356	171
		domInteractive	13	168	46	32	16

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 89 Bytes (0.00%)
• common: 0 Bytes (0.00%)