i18n: restore key parity after the Jalali calendar

The translation parity test fails on main again after the Jalali
calendar landed: the two newest locales, he and sk, were missed when
the twelve Jalali month names were added - they get the same Latin
transliterations every other non-Persian locale received.

fa in turn carried four keys that do not exist in en and are not
referenced anywhere in the code (the email_composer.text_direction
block and settings.templates.image_too_large) - removed, as the
suite's no-extra-keys check demands.

locales/fa/common.json

@@ -681,12 +681,7 @@
     "recipient_email_placeholder": "آدرس ایمیل",
     "recipient_name_placeholder": "نام نمایشی",
     "autocomplete_search_server": "جستجو در سرور",
-    "autocomplete_searching": "در حال جستجو...",
-    "text_direction": {
-      "toggle": "تغییر جهت متن (چپ‌به‌راست / راست‌به‌چپ)",
-      "ltr": "چپ‌به‌راست",
-      "rtl": "راست‌به‌چپ"
-    }
+    "autocomplete_searching": "در حال جستجو..."
   },
   "confirm_dialog": {
     "confirm": "تأیید",
@@ -1885,8 +1880,7 @@
       "validation": {
         "empty": "نام قالب الزامی است",
         "too_long": "نام قالب باید ۲۰۰ کاراکتر یا کمتر باشد"
-      },
-      "image_too_large": "حجم تصویر بیش از حد مجاز (حداکثر ۱ مگابایت)"
+      }
     },
     "files": {
       "display": {