UX: Show an obvious timeout error instead of a generic one (#216)

There are times when using the DiscourseAi translator that we will face a Timeout::Error due to FinalDestination resolver. This will result in a generic error surfaced

This commit makes it obvious that the user can try again

app/services/discourse_translator/base.rb

@@ -78,7 +78,11 @@ def self.access_token
     end
 
     def self.save_translation(translatable, target_locale_sym = I18n.locale)
-      translation = yield
+      begin
+        translation = yield
+      rescue Timeout::Error
+        raise TranslatorError.new(I18n.t("translator.api_timeout"))
+      end
       translatable.set_translation(target_locale_sym, translation)
       translation
     end

config/locales/server.en.yml

@@ -27,6 +27,7 @@ en:
     not_supported: "This language is not supported by the translator."
     too_long: "This post is too long to be translated by the translator."
     not_available: "The translator service is currently not available."
+    api_timeout: "The translator service took too long to respond. Please try again later."
     amazon:
       invalid_credentials: "The provided credentials for AWS translate are invalid."