Change display and translations structure for criteria and concepts

[juliangruendner]

the translation structure should be change to allow for distinguishing between original display values and translations by language.

This should be changed for the criteria search and the concept search alike.

For the ontology index (criteria search) the display replaces the attribute "name".

{
    "availability": 0,
    "terminology": "http://loinc.org",
    "termcode": "74620-6",
    "selectable": true,
    "context": {
        "system": "fdpg.mii.cds",
        "code": "Laboruntersuchung",
        "display": "Laboruntersuchung",
        "version": "1.0.0"
    },
    "termcodes": [
        {
            "system": "http://loinc.org",
            "code": "74620-6",
            "display": "1,1-Dimethoxy-(9Z)octadecene (DMA 18:1)/Oleate (C18:1w9) [Mass Ratio] in Fibroblast",
            "version": "2.77"
        }
    ],
    "display": {
        "original": "1,1-Dimethoxy-(9Z)octadecene (DMA 18:1)/Oleate (C18:1w9) [Mass Ratio] in Fibroblast",
        "en-US": "1,1-Dimethoxy-(9Z)octadecene (DMA 18:1)/Oleate (C18:1w9) [Mass Ratio] in Fibroblast",
        "de-DE": "1,1-Dimethoxy-(9Z)octadecene (DMA 18:1)/Oleate (C18:1w9) [Masse Verhältnis] in Fibroblast"
    },
    "criteria_sets": [],
    "parents": [],
    "children": [],
    "related_terms": [],
    "kds_module": "Labor"
}

{
    "termcode": {
        "code": "0200",
        "display": "Geriatrie",
        "system": "http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel",
        "version": 2099
    },
    "value_sets": [
        "http://fhir.de/ValueSet/dkgev/Fachabteilungsschluessel"
    ],
    "display": {
        "original": "Geriatrie",
        "en-US": "Geriatrix",
        "de-DE": "Geriatrie"
    }
}

When delivering this via the rest api however, the "display" object will be converted so it matches the format introduced in #381

[michael-82]

After a quick discussion we decided to slightly change the format (the internal one for elastic search) so we do not use an array for translations. Since this would introduce a need for nested field type, which brings some restrictions, for which I honestly can't estimate if it will be a bigger deal in the future. So for now we will keep it simple.

[juliangruendner]

"display": {
            "original": "MII PR Medikation MedicationRequest",
            "translations": [
              {
                "language": "de-DE",
                "value": ""
              },
              {
                "language": "en-US",
                "value": "MII PR Medikation MedicationRequest"
              }
            ]
          }