Enable useful component checks in glossaries

### Describe the problem

Formatting issues in glossary terms such as missing ellipsis, starting and trailing spaces/newlines etc. are not detected because the checks only apply to the _translated strings_ or _source strings_ scope but not the _glossary strings_ scope.

### Solution brainstorm

Identify which checks also "make sense" in glossaries and expand their scope to include glossary strings.

### Describe alternatives you have considered

- A "use all string checks" checkbox in the glossary section of the basic component that enables the same checks as in a normal component: yet another setting to decide on, and can lead to useless checks being enabled

### Screenshots

_No response_

### Additional context

_No response_

Start by locating the glossary strings scope and the existing component string checks. Identify which formatting checks apply to glossary terms without enabling irrelevant checks; done means useful checks detect issues such as missing ellipses or surrounding whitespace in glossary strings.

Written by the indexing model from the issue text.