Draft: FEATURE: Add glossary management

[lorenzulrich]

This code is extracted from https://github.com/robert-heinig/Sitegeist.LostInTranslation/tree/feature/glossaries. Since this branch diverged heavily from the original package, I extracted all relevant changes to this branch.

This is not meant from merging as code style-wise the feature is not really in line with the rest of LostInTranslation. However, I'm pushing this as a base for discussion if we should bring this to a state that is mergeable.

This can be configured as follows:

Sitegeist:
  LostInTranslation:
    DeepLApi:
      glossary:
        backendModule:
          sortByLanguage: 'DE'
        languagePairs:
          -
            source: 'DE'
            target: 'EN'

This allows adding a glossary when DE is translated to EN. It relies on the deeplLanguage being set in the CR dimension configuration, e.g.:

Neos:
  ContentRepository:
    contentDimensions:
      language:
        label: 'Sprache'
        icon: icon-globe-europe
        default: de_CH
        defaultPreset: de_CH
        presets:
          de_CH:
            label: 'Deutsch'
            values:
              - de_CH
            uriSegment: ''
            options:
              deeplLanguage: 'DE'
          en_GB:
            label: 'English'
            values:
              - en_GB
            uriSegment: 'en'
            options:
              deeplLanguage: 'EN'
              translationStrategy: 'once'

Please be aware of the following:

• The DeepL glossary API does not allow editing a glossary item (see here). That means that every time the glossary is changed, a new glossary must be pushed to DeepL and the old one deleted. Therefore, you need to execute ./flow flow glossary:sync to set up and sync the glossary (also when installing it).
• The DeepL glossary apparently is not just a "search & replace" which will lead to unexpected results. Without enough text/context, it is possible that terms are not replaced or not replaced properly. I don't have more insight how it actually works, but found a mention of it here and have experienced the behaviour myself.

Resolves: #5
cc @robert-heinig

[lorenzulrich]

This seems to be uninteded from the original author ;-), needs to be replaced by the Site name.