Migration to Manifest Version 3

[izzy]

A newer version of the manifest exists requiring some overhaul in the general architecture of the extension.

As with the last manifest version, this opens the door(and in some cases need) for some refactoring.

More info:

• https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/
• https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/

Given this will be a major overhaul, once the changes are in, the extension should hop to a 5.0.0

[izzy]

There is a known issue in manifest v3 that makes chrome.i18n.getMessage unavailable for creating context menus from the background page:

1159438 - chrome.i18n.getUILanguage API unavailable from manifest v3 extension's background ServiceWorker - chromium

While chrome.i18n.getUILanguage is supposedly available building anything around that function would be a lot of work while being janky at best. Therefor not buiilding the extension aroudn i18n.getMessage seems like a waste of time.

See also w3c/webextensions#93

[izzy]

The issue seems fixed in the current canary version(100.x), which should become beta in March and stable in April. https://bugs.chromium.org/p/chromium/issues/detail?id=1268098#c11