should fix the bug related to config override within a project's dev-setup

[hoatle]

please check this project: https://github.com/hoatle/teracy-dev-override-bug and follow the README file to reproduce

To fix this:

• unit tests are required to reproduce the bug
• code changes to pass the failing unit tests

[hoatle]

there is a workaround by adding:

      "data_configs": [{
        "_id": "data_configs_0"
      }]

into the workspace/dev-setup/vagrant_config_default.json file

[phuonglm]

I'm going to update the strategy/order of config merge as follows:
Old order:
(teracy-dev + teracy-dev-override) + (org + org-override) + (project1 + project1-override)
New order:
(( teracy-dev + org) + ( teracy-dev-override + org_override)) + project1 + .. + projectx + project1_override + .. + projectx_override

The new order lets the default configuration build the frame, then we can use override configuration files to change the frame.

[hoatle]

seems that we have a regression here, please see: #386 (comment)

[hoatle]

@phuonglm I'll possibly revert the related code changes for this in 12 hours until we get the working solution to prevent blocking other devs to continue working on the develop branch. This issue is blocking for such a long time without any progress.

[hoatle]

reverted