preferences: toggling 'auto-save' should update user settings

[vince-fugnitto]

Bug Description:

The framework incorrectly updates the editor.autoSave preference when toggled (through the menu or command), by updating the value in the workspace scope rather than user. We should align the behavior to use the user scope by default similarly to vscode.

autoSave.mp4

Steps to Reproduce:

1. remove any custom preferences from the user home (for test purposes - ex: rm -rf ~/.theia).
2. create a temporary folder with a single file (no .theia should be present).
3. toggle the autoSave command.
4. notice that a .theia folder is created in the workspace with the setting.

[AbhiSahane0]

This issue is still open.

[AbhiSahane0]

Can I go a head to work on it

[vince-fugnitto]

Can I go a head to work on it

@AbhiSahane0 unfortunately I do not believe it is a straighforward issue for beginners to pick up, we will require investigation, debugging and in the end discussions on how to fix the preferences-system (which is core to the framework) in order to achieve a proper solution rather than a patch fix.

[AbhiSahane0]

Okk , Sir

[colin-grant-work]

I'll pick this up, since I'm pretty familiar with the workings of the preference system.

[kittaakos]

The framework incorrectly updates the editor.autoSave preference when toggled (through the menu or command), by updating the value in the workspace scope rather than user. We should align the behavior to use the user scope by default similarly to vscode.

I am not sure if this is a bug. I also prefer the VS Code UX, (save this config with a user scope) but you cannot just change the runtime behavior that downstreams have been using for years now. What about adjusting it for electron? Thoughts?