When updating the object's alias for a content translation that already existed, the alias history no longer refers to that translation.
This results in the history url not being available for any siteacces that does not use other languages.

Steps to reproduce:

1. For test purposes, make sure there is an 'eng' (default) and 'fre' language / siteaccess
2. Verify the following [RegionalSettings] for the 'fre' siteaccess:

   ShowUntranslatedObjects=disabled
   SiteLanguageList[]
   SiteLanguageList[]=fre-FR
   

3. Create an article 'Article1' in Eng,
4. Add a new translation, 'Article1' in Fre
5. Update the Fre translation to 'Article2'
6. On the frontend, using the 'fre' siteaccess, verify that the old 'Article1' alias (history) is not reachable.

Expected Result:

The old url alias should be kept, referring to the new 'Fre' content translation
(see https://doc.ez.no/eZ-Publish/Technical-manual/4.x/Features/Multi-language-support-for-URL-aliases , "URL history entries" )

Other notes:

In the ezurlalias_ml table, the language mask for the alias history is updated and the code for 'Fre' translation is removed.
Before:

+------------+-----+-----------+-------------+
| action     | id  | lang_mask | text        |
+------------+-----+-----------+-------------+
| eznode:119 | 106 |         4 | Article1    |
+------------+-----+-----------+-------------+

After:

+------------+-----+-----------+-------------+
| action     | id  | lang_mask | text        |
+------------+-----+-----------+-------------+
| eznode:119 | 106 |         2 | Article1    |
| eznode:119 | 106 |         4 | Article2    |
+------------+-----+-----------+-------------+