Avoid reseting config on parse error

[maelp]

For now if there's an issue with the config JSON file (eg an additional "," or something) it will silently reset it and lose configuration
It should at least ask before doing that, or tell the user to fix it

[geekforbrains]

Agreed. The current implementation is a stop-gap. I was thinking some sort of migration system, so when new changes are added, Sidekick would migrate the required fields. For full on errors though, perhaps it makes a backup of the existing config and tries to extract values from the broken config? I'll explore some ideas here.