Issue #1156458 by Gábor Hojtsy: move menu translation functionality to translation tabs consistent with taxonomy, blocks, etc.

Issue #1078422 by danielnolde, tobiasb: Disabled taxonomy fields when enabling and disabling i18n_taxonomy

Issue #1156374 by Gábor Hojtsy: try to guide users to the taxonomy page where they can actually make edits and translations - not the best solution, but core already has this UX WTF, so we need to live with that

Followup to #1155238 by Gábor Hojtsy: add translate tab on vocabulary and move the translation set feature around, so that it sits with the term list, not to confuse users

Follow up to #1155238 by Gábor Hojtsy: add translation tab support for localizable terms using our general tools in i18n_string module

Followup to #1155156 by Gábor Hojtsy: redirect the user back to the translation page, when they save a translation of an object

Issue #1155472 by Gábor Hojtsy: remove locale_refresh implementation since the listing function now does this all

This reverts commit c80d9ee0.

Issue #1155218 by berdir, Jose Reyero, Gábor Hojtsy: i18n_string_remove_string() does not exist, i18n_string_remove() does

Issue #1155156 by Gábor Hojtsy: add support for contact module translation; also apply the new i18nstrings translation tab concept

Issue #1114602 by Gábor Hojtsy, yoroy: improve usability of i18n_string based modules dramatically by providing an API to expose a translation tab on objects
Reference implementation of that on blocks.