because we did not delay the readiness of the application when loading
translations when a user hit `update-setting` route we'd render the page before
the language had finished loading. Moving the language to the before model and
in the finally of the detect phase ensures we have our language loaded before we
remove the loading state and render the main content.
rancher/rancher#23776
remove prototype extension
Remove translations from engines
The motivation behind this change stems from this issue ember-intl issues/797
and the current implmentation of engine support in ember-intl. The translations
essentially get bundled twice. Until ember-intl removes the second bundle it
makes sense to keep the translations in the main ui file.