Make glossary terminology available in all linked project languages

### Describe the problem

A glossary always has the full set of languages of it's project available as translations. Terms in the glossary which are marked as terminology are also automatically created in all languages in of that project.

But when the glossary is shared into another project where there are different languages, the terminology terms are not available in those languages.

### Solution brainstorm

Change the way terminology terms are selected in the component in the linked project, do not require the language to exist in the glossary.

### Describe alternatives you have considered

- Creating the languages of the linked project: will "pollute" the project of the glossary with unwanted languages, and leave left-overs when the link is removed again.

### Screenshots

_No response_

### Additional context

_No response_

Start by tracing the component that selects terminology terms for a linked project. Verify how glossary and linked-project languages are currently compared, then confirm the change makes terminology available in every linked-project language without creating those languages in the glossary project. Add or update focused tests for both matching and non-matching language sets.

Written by the indexing model from the issue text.