Making updates to handle different iso codes.

[THOR300]

Description

The current backend code assumes that language codes send to the update document endpoint will be if the for iso-639-3. This is a three letter representation of the language.

The pipeline identifies languages as iso-639-1 which is a two letter representation.

Thus, the endpoint is updated to handle the differing language codes. A unit test is also added to check functionality.

NOTE:
Should we update the languages table to enforce part1_codes being unique and len(2) as the functionality will rely on that an in practice the two letter codes should be unique and two letters (the same of language codes and three letters)?
Should we also at least log when we pass over a language update due to it not existing in the database?

Linear Ticket

Type of change

Please select the option(s) below that are most relevant:

• Bug fix
• New feature
• Breaking change

How Has This Been Tested?

Unit test in the PR

Reviewer Checklist

• The PR represents a single feature (small driveby fixes are also ok)
• The PR includes tests that are sufficient for the level of risk
• The code is sufficiently commented, particularly in hard-to-understand areas
• Any required documentation updates have been made
• Any TODOs added are captured in future tickets
• No FIXMEs remain

[joel-wright]

This certainly adds support for 2 letter codes.

[joel-wright]

Looking good :)