Add support for organization-level Concordance search

[crowdin-bot]

The Crowdin API adds organization-level concordance search endpoints that search across all accessible glossaries and translation memories (the existing concordance endpoints are project-scoped):

• Concordance search in Glossaries — POST /glossaries/concordance (api.glossaries.concordance.post). Request body: sourceLanguageId (string, required), targetLanguageId (string, required), expressions (array of strings, required).
• Concordance search in TMs — POST /tms/concordance (api.tms.concordance.post). Request body: sourceLanguageId (string, required), targetLanguageId (string, required), autoSubstitution (boolean, required), minRelevant (integer, required), expressions (array of strings, required).

On crowdin.com both request forms additionally accept an optional nullable userId (integer); this field does not exist in Crowdin Enterprise. Responses reuse the existing concordance result models.

Client libraries should add these organization-level methods alongside the existing project-scoped concordance search.

References:

• Concordance search in Glossaries
• Concordance search in TMs
• Crowdin Enterprise: Concordance search in Glossaries, Concordance search in TMs

[jjj-n]

Hi, I'd like to work on this issue.

I plan to add organization-level concordance search methods for glossaries and translation memories, reuse the existing response models, add the required request models, and cover both endpoints with focused mock-based tests and JSON fixtures. I'll preserve the existing project-scoped APIs and Java 8 compatibility.

Could you please assign this issue to me?