Multilingual nested fields are not translated in the UI

**Describe the bug**
If a metadata is multilingual, nested indexed fields are not well interpreted in the UI.
Example: `contact.organisation`

@fxprunayre have you encountered such behavior, no contact is multilingual on your catalogs ? Is it a reported bug or do you plan to work on it ?

If not, we will add the `Object` suffix in the index eg. `organisationObject` and make the process which translates the fields in `Metadata.CatalogService` recursive.

Any feedback would be appreciated.
Thanks

Start by tracing multilingual nested-field handling in Metadata.CatalogService, using contact.organisation as the example case. Confirm how the UI interprets the indexed field and determine whether nested translation works; done means multilingual nested fields are rendered correctly in the UI.

Written by the indexing model from the issue text.