Long summary translation fix

The 'context saving' setting for do-not-translate protection was added. Can be managed by the 'Enable context saving for do-not-translate protection' checkbox

Bug fix: Fix availability for translations comments in issues lists.

Bug fixes:

1. Move the routing detection from the client to the server.

2. Fix the Table formatting issue.

TECH RELEASE: Configuration of roles-required specified at the <webwork1> level but not the <action> level to prevent exploiting the CVE-2022-0540 vulnerability

TECH RELEASE: Spring Framework version upgraded to 5.3.21 to prevent exploiting the CVE-2022-22965 vulnerability

* Upgraded RegEx text protection to work in multiline mode. That gives the ability to the users to instruct ITJ on the project level on which text not to send for translation, e.g., the text inside some tags.

* previously added protection of English phrases in Japanese texts is removed (it is now handled by the MT providers)

• MT can be requested after human translation
• New Intento logo

• Introducing an option to customize summary's separator for human translation. If a summary does have a human translation, then no machine translation will be applied to the summary.
• Frontend requests were optimised

Upgraded the version of Atlassian spring scanner

Logging levels optimization

Bug fix

We fixed a bug with the icons in the comments – now comment translation is available in backlog and sprint views.

Now you can choose a Technical user. When invoking translation, this technical user will update tickets and comments with the translation results.

All project users can translate any ticket's comment - no dependency on "Edit Comment" permission.

• Support for Jira formatting
• Improved language detection
• Release to Jira Data Center Marketplace