Remote Functions Refactor

Overview

Remote functions exist to enable background->tab, and tab->background function delegation (i.e. Call a function in a tab, but have it run in the background and vice versa).

Refactoring has been started to make these functions interfaced and type safe.

Tasks

Grepping the codebase for remoteFunction( shows where it's still being us

Description:

Provide option to keep some segment and provide a submit button below each segment as I don't want to upload the first segment. As I want the first segment but not sure about the consensus and correctness about the first segment.

Is your feature request related to a problem? Please describe.
We have many Japanese and Chinese speaking users but the interface is only in English

Describe the solution you'd like
Develop an i18n that detects the user language and adapting all the labels accordingly

Describe alternatives you've considered
Let the user select the interface language

Additional context

When a user would like to use yarn, it needs to be installed, even when --skip-install option is used.
I think this check could be moved to the actual install phase, simply throwing a warning like "Yarn is not installed, skipping install. Please install yarn on your machine." is enough.
What do you think, @HaNdTriX ?

The module we use (https://github.com/TinyWebEx/AddonSettings) does abstract all the settings of the add-on and by default tries to query the option as a managed option first. Thus, any setting we use, should theoretically be able to be overwritten by an administrator and the user should not be able to change it, afterwards.
The module [for the options page](https://github.com/TinyWebEx/Automatic

Fonts are stored inside src/fonts/googlefonts and we treat them as static assets. To make it available to our HTML pages we use a webpack plugin that gets a list of all the static assets which is provided by config/webpack/static-files.js. The font files are hardcoded but instead, this needs to be dynamically added to the static files list by reading all the font files inside src/fonts.

any ideas?😄

At the very least, tests for the core parsing code would be great. As new languages are added for localization it would be very helpful to ensure the new patterns are all in alignment.

UI testing is likely not feasible with the extension architecture (someone prove me wrong and I'll be happy).