Convert bsconfig merging into a deep clone

Currently, bsconfig.json files can be extended. (i.e. your bsconfig.json extends base.bsconfig.json). As such, the current logic does a shallow merge of the two. Something to this effect:

var config = {     
    ...getDefaults(),     
    ...getConfig('base.bsconfig.json'),     
    ...getConfig('bsconfig.json') 
};

What this means is, for arrays and objects, the child completely overrides the parent. So if you wanted the base.bsconfig.json to specify some entries in files and the child to specify some more, this would not work. The child's files array would totally override the parent's.

We should use a deep copy of all bsconfig.json values when using extends or project

Locate the configuration-loading and merge logic used by bsconfig.json extends and project settings. Start by tracing how base.bsconfig.json and bsconfig.json values are combined, then inspect any existing configuration tests. Done means nested objects and arrays from the parent and child configurations are combined without the child unintentionally replacing all parent entries.