feat: migrate to google manifest v3

[listen1]

related info from google

We recently published a timeline of our plans to move forward with the deprecation of Manifest V2 and shifting focus fully to the new iteration of the platform. This is a notice that beginning January 17, 2022, the Chrome Web Store will stop accepting any new Manifest V2 extensions with visibility set to “Public” or “Unlisted”. Existing Manifest V2 extensions that have previously been published publicly will not be affected by this change and updates to those already-published extensions will continue to be accepted.

Additionally, beginning in June of 2022, this restriction on new extensions will expand to include items set to “Private” visibility as well. For more details and dates relating to the phase-out of Manifest V2, please refer to the Manifest V2 Support Timeline page, which will be kept up to date as more exact dates and milestone details are available.

Summary: V2 Updates are still accepted, but new public v2 extension will not be accepted since 2022/01/17

[Dumeng]

January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store. Developers may still push updates to existing Manifest V2 extensions, but no new Manifest V2 items may be submitted.

January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions.

One more year until MV2 is fully deprecated. Reference

Although the new Edge should follow this specification cause it's Chromium based, Firefox may not going to use the same specification by Google. Reference

[listen1]

Firefox manifest v3 news letter:

Manifest v3 coming to Firefox in 2022

To maintain compatibility with other browsers, we are currently in the process of making a set of changes to Firefox’s extensions API known as “Manifest v3.” These updates will help keep Firefox compatible with other web browsers to make it easier for you to publish your extensions on multiple platforms.

Manifest v3 will introduce several new functional changes, including:
Replacing background pages with background service workers
Disabling dynamic code execution in privileged extension contexts by default
Introducing a content security policy for content scripts
You don’t need to take any action for your extensions around Manifest v3 at this time. We’ll let you know when early testing is available in the Nightly pre-release channel, which will likely be later this year. In the meantime, please let us know about any specific use cases we should keep in mind to keep your extension compatible on our community forum.

[listen1]

migrate to google manifest v3 will be done after tested in chrome/firefox/edge supported.
before that, we still use v2 version until chrome store stop accept v2 update.

[listen1]

#817