Unify the `configurarion-name` and `overriden-properties` into one `configurations.json` file.

[denis-shienkov]

Right now we use the separate overriden-properties.json file to store the overriden properties, and the separate build configurations button on the status bar.

In this case it is impossible to assign the overriden-properties for the specific build configuration.

The solution is to get rid of the overriden-properties.json file in vafor to the configurations.json file. In this case this configurations.json file may contains all build configurations and its overriden properties e.g. in a such format:

{
    "release": {
     // "key": "value" 
     },
    "debug": {
     },
    "profiling": {
     }
}

where the release, debug, profiling (or something custom) - are the build configurations maps, and the underlying dict is the map containing overriden-properties for each configuration (it is key -> value pairs).

Also we need to do the additional changes:

• Introduce the "Edit build configurations" command, which should create the default configurations.json file if it not exists yet, and then to open this file in the editor.
• Modify the "Select build cnfiguration" command to parse this configurations.json file to select the desired configuration.
• Also we need to modify the build step to take the curent selected build configuration from the configuration.json file.

[denis-shienkov]

Right now it is implemented with the following configurations.json format:

[
    {
        "name": "release",
        "display-name": "Release",
        "description": "Enable optimizations.",
        "overridden-properties": {}
    },
    {
        "name": "debug",
        "display-name": "Debug",
        "description": "Disable optimizations.",
        "overridden-properties": {
            "projects.foo.hasSpecialFeature": false
        }
    },
    {
        "name": "profiling",
        "display-name": "Profiling",
        "description": "Enable profiling.",
        "overridden-properties": {}
    }
]

where the :

• name - is the mandatory build configuration name (will be passed to qbs)
• display-name - the text which will be displayed on the Select Configuration button and in the Select Configurations selector.
• description - a short brief which will be displayed in the Select Configurations selector.
• overridden-properties - it contains the set of properties which should be overridden (will be passed to qbs)

[denis-shienkov]

UPD: File configurations.json renamed with qbs-configurations.json.