This PR adds translation flow to the electronjs wrapper

The approach is following:

• as electronjs wrapper must be launched first before UI, the language selection management functionality needs to be electronjs driven
• provides ability to get/set language in UI using injected API by built-in electronjs mechanism over IPC https://www.electronjs.org/docs/latest/tutorial/ipc
• on the first launch, the app detects OS default language https://www.electronjs.org/docs/latest/api/app#appgetpreferredsystemlanguages
• the UI has API:

window.bfxReportElectronApi.setLanguage('en') // return either false (if not set) or `i18next.resolvedLanguage` eg 'en'
window.bfxReportElectronApi.getLanguage() // return eg 'en'
window.bfxReportElectronApi.getAvailableLanguages() // return eg ['en', 'ru', 'es']

• if language is changed via UI, the provided API persists value into storage on the electronjs process side
• and the next time the language value returns from that storage

Basic changes:

• store translations in one common folder
• separate translations by language in JSON files using namespaces
• use i18next lib and the official i18next-fs-backend plugin to provide the ability to load translations
• provide correct i18next initialization in the main entry point
• add translation ipc channel bridge to window preload script to have window.bfxReportElectronApi on UI side
• add translations into the main menu of the app
• provide ability to use the UI dev server with the electronjs wrapper in dev mode to be able to develop the corresponding UI part of this feature. For this purpose adds concurrently dep https://www.npmjs.com/package/concurrently to the dev section. Provides corresponding cmd:

npm run startWithUIOnPort

Here in parallel launch the UI dev server and the electron wrapper that waits for localhost:3000 for 1min to be initialized