Set plugin titles from locale

[arturi]

• Trying to move i18nInit to the BasePlugin class, since around 70% of the plugins use locales, and right now we have this dance duplicated in each of them. Good idea?

i18nInit () {
  this.translator = new Translator([this.defaultLocale, this.uppy.locale, this.opts.locale])
  this.i18n = this.translator.translate.bind(this.translator)
  this.i18nArray = this.translator.translateArray.bind(this.translator)
  this.setPluginState() // so that UI re-renders and we see the updated locale
}

• Using locale keys like pluginNameInstagram, pluginNameWebcam to group them in the locale file and distinguish from general keywords like Camera or Webcam vs pluginNameWebcam.

Closes #2279

[aduh95]

Could we move translator and i18nArray to private properties?

[arturi]

Yes, you mean the new # thing? I think so, shouldn’t be public.

[goto-bus-stop]

i18nArray should be accessible by subclasses so they can use it in preact code

[aduh95]

Let's get rid of those bind calls.

E2E tests are failing (packages/@uppy/locales/src/en_US.js issue again).

[aduh95]

Is this still necessary if Transloadit extends BasePlugin?

uppy/packages/@uppy/transloadit/src/index.js

Lines 90 to 95 in 9a46b0d

	i18nInit () {
	this.translator = new Translator([this.defaultLocale, this.uppy.locale, this.opts.locale])
	this.i18n = this.translator.translate.bind(this.translator)
	this.i18nArray = this.translator.translateArray.bind(this.translator)
	this.setPluginState() // so that UI re-renders and we see the updated locale
	}