Remove hard coded English-only semi-localization from language names

In the process of trying to get a completely localized interface (see also #33 and #32), one thing that was sticking out was the hard coded English strings attached to language names. As explained in the commit message for 4a53bc6, I believe these to be unnecessary and cumbersome.

I would suggest ditching them entirely in favor of just using localized language names. People are going to know where to find and how to read the languages that are of interest to them. Non English speakers are actually going to recognize more of the localized names than they will the EN names.

The only exception that comes to mind is not important for the language selector menu so much as for the names of translations. Namely for Greek and Hebrew I know there are some users with an interest in texts in those languages that don't actually know beans about them. Whether these are the sort of users you want to cater to or not is something I would question¹, but let's assume for now you do. These are a strange beast anyway as the content modules are often catered to an English audience even though the content may be in Greek or Hebrew. The GWH module for example has English delimiters inline in the Greek text.

In any event the current module names are in English anyway, so for now the English usage isn't broken and localizing translation names is something I'll be playing with in my [localization-languages](https://github.com/alerque/browserbible-3/tree/localization-translations) branch and save for a later PR when it gets sorted out.

¹ <sub>If they can't find «עִבְרִית» in a menu how useful is it going to be for them to start readingבְּרֵאשִׁ֖ית בָּרָ֣א» אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃»?</sub>