Wrong i18n usage cause some unexpected TypeError

[backrunner]

Wrong i18n usage cause some unexpected TypeError

[acid-chicken]

some languages contain {n} expression, and some not

Good catch!
The current logic implicitly assumes that the presence or absence of parameters is consistent across all languages, and indeed they should be.
However, there was no mechanism to check for these in the current localization process.
Rather than changing the application logic, this process should be revisited (e.g. CI check for locale parameters).

[dakkar]

https://activitypub.software/TransFem-org/Sharkey/-/merge_requests/493 should fix the "account migration" bits, at least