Fix translations junction field not using language table name

[azrikahar]

Fixes #12255

Before

Whenever we change the language table name during creation of Translations field, the junction field always remains as languages_id instead:

chrome_Rp1tPvbnPl.mp4

Solution used

For m2m, whenever relation.m2o.related_collection has changed, it will call the autoGenerateJunctionFields function:

directus/app/src/modules/settings/routes/data-model/field-detail/store/alterations/m2m.ts

Lines 22 to 25 in d640fe9

	if (hasChanged('relations.m2o.related_collection')) {
	preventCircularConstraint(updates, state, helperFn);
	autoGenerateJunctionFields(updates, state, helperFn);
	}

which then always updates the junction field name:

directus/app/src/modules/settings/routes/data-model/field-detail/store/alterations/m2m.ts

Line 139 in d640fe9

set(updates, 'relations.m2o.field', `${relatedCollection}_${relatedPrimaryKeyField}`);

Hence this solution uses a similar logic with updateJunctionRelated function to update said field.

After

chrome_7svCIjbDzj.mp4