[FEATURE] Define casings on glossary items

[joey-bolts]

Is your feature request related to a problem? Please describe.
As far as i have seen now the glossary seems to be case sensitive. This means glossary words at the start of the sentence with different casing compared to the glossary definition do not get translated correctly.

Describe the solution you'd like

• Typoscript configuration which also synchronises different casings of the defined words.

Describe alternatives you've considered

• TCA multiselect field with different casing options e.g. where word gets synchronised accordingly to the api.

Would love to have feedback on this issue, since now editors have to add alot of duplicates with casing possibilities.