Normalize organisation name value for ISO19110 metadata.

[josegar74]

If not normalized, add-multilingual-field receives in elements the gmd:organisationName node and util:escapeForJson(.) was adding a breakline for the child gco:CharacterString. This caused the organisation name facet in the search to display a prefix OrgForResourceObject.default - in the organsation name

Test case:

1. Create and iso19110 metadata and define the contact organisation name
2. Go to the search page and check the organisation name facet:

• Without the fix: the facet value shows a prefix OrgForResourceObject.default -
• With the fix: the facet value shows only the organisation name.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation