Transition to Manifest v3

[ItsVipra]

When trying to run the addon in Chrome (113.0.5672.127) there are several problems at the moment:

1. The 'browser_specific_settings' manifest key is not recognized
2. Manifest v2 is no longer supported in chrome
3. "browser" is not defined - use "chrome" instead of generic browser?

Originally posted by @ItsVipra in #4 (comment)

---

Manifest v2 is no longer supported in Chrome, so we should transition to v3 to support Chrome(ium).

Implementation

See https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/

[ItsVipra]

after much frustration i've come to the following conclusion:
manifest v3 on firefox is broken or something? doesn't request permissions correctly. Fediact (yes i reference that extension a lot) also uses manifest v2 for the firefox version exclusively.
it seems like nobody on firefox uses v3 if they don't have to, even big extensions like ublock. thanks for nothing google >:c

my best guess on how to handle this is to upgrade the manifest file to v3 for chrome and implement a toolchain that converts it back down to v2 for our firefox release

[nachtjasmin]

even though there’s some progress in #15, the upcoming Firefox release might make the transition easier.