Set preferences are, by default, set in the context in which they are defined.

For example, if a preference is set at the "user" level and the user changes
the value via UI, the preference will be changed at the "user" level. If it's
set in a .brackets.json file, the preference will be changed there.
If the preference is defined only at the "default" level, it will be set
at the next higher level of precedence ("user" level in our setup).

This is a fix for #6595.
Properly reconfigure the user prefs in test windows.

This is a fix for #6575.
Maintain the original line endings in preferences files
Merge pull request #6603 from adobe/dangoor/6575-prefman-test

Properly reconfigure the user prefs in test windows.
Changes based on review comments
Better doc comment for `Scope.set`
Merge pull request #6602 from adobe/dangoor/6595-pref-set

Fix for 6595: Set preferences are, by default, set in the context in which they are defined
Define self to prevent exception, for #6607
Merge pull request #6608 from adobe/nj/issue-6607

Define self to prevent exception