Test syntactic correctness after translation

[janezd]

Currently, https://github.com/biolab/orange-translations runs a github action that

• runs trubar translate
• checks syntactic correctness of entire project afterwards.

The second step wastes time (not all sources were changed) and, more importantly, could already be done by trubar after translation.

trubar should have an option (either in configuration, or command line (--nocheck), or both) to check sources after translation. To save time, check would only be run if target file was translated (not copied) and the translation differs from previous translation.

While implementing this, you can also improve the output by allowing different levels of verbosity. Report either

• copying and translating (the current output)
• only translating,
• translating, but only if translation differs from previous.

[janezd]

Translated source is generated by calling ASTs tree.code_for_node, which is unlikely to be syntactically incorrect. The only possible source of problem would be incorrect auto-import config option, but this is very unlikely to go undetected for long.

Neither trubar nor orange-translation need to check the syntax of the output.

It would be, however, beneficial to reduce the output clutter.