Add glossary check for source stings problematic in CSV

[nijel]

Describe the problem

Some strings can't be exposed in CSV to automatic translation backends (see https://github.com/WeblateOrg/weblate/issues/12791). Weblate should warn that these are problematic.

Describe the solution you would like

Add glossary only check to warn about using any of =+@- at the beginning of the string for both source and translation.

Describe alternatives you have considered

https://github.com/WeblateOrg/weblate/issues/12791 will deal with such strings, but these will be missing from the sync (or problematic characters stripped), so user should be notified of that.

Screenshots

No response

Additional context

Currently, no checks are triggered on glossary components:

https://github.com/WeblateOrg/weblate/blob/64aa009bb957309a6938724b2e493ff69354c49c/weblate/trans/models/unit.py#L1353-L1355

[github-actions[bot]]

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, don’t hesitate to support Weblate by making a donation.

[gersona]

@nijel you reopened the issue after #12806 was merged, is there anything that needs to be corrected ?

• 12806

[nijel]

That addresses https://github.com/WeblateOrg/weblate/issues/12791. There still remains this issue to let user be aware that something is wrong with the glossary term.