problem

The main reason why we did not implement a config editor for the map typed configs was, that some values are real json and not only a map / assoc array config. So this was postponed from TRANSLATE-471.

solution

• Introduce a new config type json (basically the same as the current map), set all map types to json.
• Convert all configurations where the value is a real 2d map value back to map, set them to the appropriate config level as formerlly defined in TRANSLATE-471
• Implement an editor for that map, either a propertygrid if adding, removing, renaming of properties is possible, if not just use a simple roweditor grid (from the examples)