Possibility to override the primary glossary for a module

### Describe the problem

Hello,

I have been working on the translations for the [«Game: NodeCore» module in the MineTest project](https://hosted.weblate.org/projects/minetest/nodecore/it/). The project has two glossary modules: a project-wide «MineTest Glossary», and a module-specific «NodeCore Glossary». The latter was added recently, in an effort to help translators that work specifically on the NodeCore game translation. When working on translations for the «Game: NodeCore» module, entries from both glossaries are available, but the MineTest glossary is the primary one (and the only one to which terms can be added in fly-by, due to issue #7549).

### Describe the solution you'd like

It would be nice if specific components could indicate a different glossary module as their primary glossary. In the mentioned case, for example, the glossary-nodecore glossary could be set as the primary glossary for the nodecore module, and would be the default target for all actions involving the glossary (including adding new terms, getting suggestions with potentially different translations in the two glossaries, etc).

### Describe alternatives you've considered

_No response_

### Screenshots

_No response_

### Additional context

_No response_