Make iThenticate reports work with new TCA integration

[MusikAnimal]

No description provided.

[JJMC89]

Make sure it is one of the supported locales.

[MusikAnimal]

The docs said it would fallback to en if unsupported, so I figure this couldn't hurt

[JJMC89]

Consider whether any viewer_permissions should be set. Some could be useful to reviewers.

[MusikAnimal]

I've added may_view_submission_full_source, may_view_match_submission_info, may_view_document_details_panel and may_view_sections_exclusion_panel. The others didn't seem to do anything or didn't work.

[JJMC89]

TCA can be down (e.g., maintenance). Does this need any special handling for that?

[MusikAnimal]

I've added automatic retries up to 5 times. I'm only checking if the response from Turnitin is not 200, so it's possible we'll needlessly retry when it's something on our end (i.e. bad credentials), but regardless we'll get an email (once I set that up) so we'll be able to diagnose and fix accordingly.

[JJMC89]

I temporarily deployed 3cd248c and got 500 when trying to view reports (ithenticate route). Rolled back to 6b18613.

[MusikAnimal]

I temporarily deployed 3cd248c and got 500 when trying to view reports (ithenticate route). Rolled back to 6b18613.

I've re-deloyed it and it seems to be working fine.

I checked the logs (~/var/log/prod.log) and the errors I see are a bit baffling. One thing I did that probably fixed it was ran webservice shell then composer install, which in turn will clear the cache (you can do so manually in the container with ./bin/console c:c --env=prod). There were composer changes but it was just adding an ext-json requirement which was already met, so everything should have worked with a simple checkout of the commit.