Add API for glossary

[twboc]

Describe the bug

When uploading a json file containing translations to the source language with endpoint:
POST /api/translations/(string:project)/(string:component)/(string:language)/file/

New fields saved in json file do not show as additianal translation just like when passing the same file with import glossary method in web client ui.

To Reproduce

Steps to reproduce the behavior:

1. Prepare json file with translations
2. Upload the file with curl passing the parameters:
   curl -X POST
   -F file=@$filepath
   -F overwrite=true
   -H "Authorization: Token $API_KEY"
   "https://hostname.com/api/translations/$PROJECT/$TRANSLATIONS_COMPONENT/$LANG/file/"
3. Open the glossary in the web client /dictionaries/app5/en/
4. See error - no additional fields from json file added.

If json file added manually glossary is updated with new fields in json file.

How to extend glossary through API

Expected behavior

Uploading a translation json file with additional keys extends the glossary.

[nijel]

You are uploading a translation, not a glossary. There is currently no API for glossary.

[github-actions]

This issue has been added to the backlog. It is not scheduled on our roadmap, but it eventually might be implemented. In case you desperately need this feature, please consider helping or funding the development.

[nijel]

Desired API:

• /glossaries/ - list glossaries user has access to
• /glossaries/(int: id)/ - get details of a glossary (name, color, source language - the last one is not yet there, will be added once Glossary: Add source language attribute #4359 is merged), PUT/PATCH to modify
• /glossaries/(int: id)/projects/ - get list of associate projects to a glossary, POST to associate another project
• /glossaries/(int: id)/project/(int: component_id)/ - DELETE to remove project from glossary
• /glossaries/(int: id)/terms/ - get list of glossary terms, paginated, POST to add new one
• /glossaries/(int: id)/terms/(int: term_id) - get term details, DELETE to remove, PUT/PATCH to modify

Access control:

• to see a glossary user needs access to any of component associated with it
• to edit a glossary attributes, user needs component.edit on any of component associated with it
• there are glossary.edit glossary.add and glossary.delete permission for editing glossary terms

[nijel]

The source_language attribute should land soon via #4359, it should support editing in a same way as on project - accept both language code or object from request.

[github-actions]

Thank you for your report, the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, consider supporting Weblate by donating.