Fix settings to pass testDefaultImageDoesNotStoreAnySetting ?

[tinchodias]

The PR to merge into Pharo 9.0 showed some tests failures.
One of them is testDefaultImageDoesNotStoreAnySetting, which I don't understand well, but finds that the following settings have something wrong:

a StoredSetting('#useCustomSsh#username')
a StoredSetting('#useCustomSsh#keyPassphrase')
a StoredSetting('#commitPreferences#saveImageOnCommit')
a StoredSetting('#commitPreferences#pushOnCommit'))

This seems to be showstopper to proceed to merge v2 so must be fixed with priority.

[tinchodias]

I just checked that the first 2 settings already make this test fail in P9.0.

By contrary, the last two are added by v2.

[tesonep]

@tinchodias does the settings have default values? Are the default values the same set "by default" by the initialization.
The idea of the test is to guarantee that a clean image does not save settings when you save settings (there all defaults, and only the non-defaults are saved).

[tesonep]

@tinchodias ping me and we check it together if you wish

[tinchodias]

Maybe these settings should be stored in the credentials store. I can ping you later.

[tinchodias]

We connected and fixed it, in dev-2.0

e734664