More i18n fixes for compatibility with WordPress

68ce179cbd8a2426dfdeaffb1971c6783a858bd5 broke the l10n technique we used in WordPress (see #849). 

When MediaElement.js tries to use `mejs.i18n.locale.strings`, the `mejs.i18n` object is already overwritten with the one that doesn't contain the strings we're trying to add. It also doesn't detect the language we're trying to pass. See http://core.trac.wordpress.org/ticket/24183#comment:8 for reference. I've also tried to set `mejs.i18n.locale` after ME.js is loaded, but that didn't work either, it appears to be too late.

SergeyBiryukov/mediaelement@adb4c7cecd934c1f7763a14ca00f4aa9aa532b16 offers two fixes to address the issue:

* Use a separate `mejsL10n` object to pass a translation as an array of
strings, to avoid conflicts with `mejs.i18n`.
* Make `getLanguage()` return just the language instead of the full locale
object.