Better yet, maybe we need a static cache for set_value where we keep track of values already saved in execution... if we try to save the same value to the same codename, we just skip it entirely. Be careful though, we should be tracking "most recent value saved", not "all values saved".

E.g. if we save 1 to kill_cron_looping, then save 0... we should still be allowed to save 1 again because we previously changed it back to 0.

Automated response: Infinite loop: kill_cron_looping

After running the Setup Wizard, you might get an infinite loop error for kill_cron_looping on step 10 if uninstalling a lot of addons / modules / blocks.

This hotfix modifies the behaviour of set_value. If we are trying to save the same value on the same codename (from the values cache), we exit the function without further execution.

Additionally, we refactored it to remove the code for deleting values; instead, $value = null will simply shortcut to the delete_value function. This is necessary for proper infinite loop detection.