ddl1-to-ddl2: casing lost during conversion

[drealeed]

It looks like the mappings are being all lowercased in upgrade.ts. This is causing dashboards not to show up due to the ddl mapping fields not matching the casing of the actual data.

ddl1cased.json.txt

[GordonSmith]

@drealeed There are two scenarios here:

1. We upgrade the DDL to v2, but leave the existing service alone (v1 hipie genrated).
2. We upgrade the DDL to v2 and upgrade the service to one generated by Hipie 2.0?

How realistic are both the above?

[drealeed]

From HIPIE and DSP-Next's perspective, #2 is the only one we'd be using.

DDL v1s will be upgraded to v2 before the service is regenerated for them. For dashboards, people will want to load an existing hipie-generated ddl1 which hipie will convert into ddl2 and load into dashy, then save, and then run. For side-effect dashboards in plugin, I have a process which converts them to a ddl2 dashboard so that when a plugin is included in a composition run, its ddl2 dashboard will be generated.

[GordonSmith]

#2864