Rename settings and the way settings are loaded

[gerardroche]

For the most part this is backwards compatible, though there are some edge-case bc breakages.

• Fixes Change Base File.sublime-settings to DocBlockr.sublime-settings #313
• Fixes PHP variable name is not being automatically generated, into the docblock, after type placeholder #334
• Fixes Fixed modify setting file have no effect #338
• Fixes ST 3103: Function name and params are not automatically transferred  #408
• Fixes Not auto completing parameter names/description #400
• Fixes "jsdoc_decorate" keybinding not working on OSX #360
• Fixes jsdocs_notation_map doesn't work for fields #397

What does it change?

1. Setting prefix is renamed from jsdocs_* to docblockr.*.
2. Settings are now stored in User/Preferences.sublime-settings instead of User/Base File.sublime-settings.

The trickiest part is making sure the refactor is backwards compatible. See here for relevant settings migration code.

Is this something that will be accepted to merge?

I'm happy to address any issues to get this change merged.

[ErichDonGubler]

Question: why not just make this use "User/DocBlockr.sublime-settings" instead? I'm using to using separate settings files for each plugin, and I don't see why we would need to use the default Preferences files here.

[gerardroche]

@ErichDonGubler There are many more problems with using named settings files than using the built-in preferences. I think it's a bad practice to use named settings files. I wrote up an explanation of this on SO: https://stackoverflow.com/a/43698128 . There are also a few other issues I didn't go into e.g. settings from named settings files are not automatically available to keymaps, in fact how would you make settings from a named settings file available to be used in a keymaps file? See the example of keymaps usage in the SO answer.

So, preferences can be used in keymaps file like so:

{ 
    "keys": [",", "a"], 
    "command": "phpunit_test_suite", 
    "context": [{ "key": "setting.phpunit.keymaps" } ] 
}

How would you do that from settings in a named settings file? There are lots of little issues like this that are solved out-of-the-box by using built-in preferences.