Escaping & character creates weird string

For #31286 (moved) we committed new strings such as

<!ENTITY torPreferences.viewLogs "View Logs&#x2026;">

When pulling the translated strings that suddenly mutated to

<!ENTITY torPreferences.viewLogs "View Logs&amp;#x2026;">

We should figure out a way where the & actually gets preserved because otherwise users are seeing the second string literally.

This bug might be responsible for XML parsing errors too, which I am seeing in the browser console.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information