Handle invalid language code gracefully in Language::fetchLanguageNames

Core MW doesn't have a problem, but translate extension explodes.
Seems safer to just use 'en' if passed an invalid language code.

Bug: 60629
Change-Id: I0ede3169bb49001a1515ae5b2b6d28477704f346
Merge "Handle invalid language code gracefully in Language::fetchLanguageNames"