Update to Chrome Extension Manifest v3

[0xdevalias]

• fixes Update to Chrome Extension Manifest v3 #13
• fixes Extension unlisted in the Chrome Web Store #21

For current status/plans/etc, refer to that issue; for example, from this comment:

• Update to Chrome Extension Manifest v3 #13 (comment)

[Copilot]

Copilot reviewed 11 out of 20 changed files in this pull request and generated 2 comments.

Files not reviewed (9)

• _locales/en/messages.json: Language not supported
• manifest.json: Language not supported
• scripts/build: Language not supported
• scripts/clean: Language not supported
• scripts/optimize-icons: Language not supported
• src/bg/background.html: Language not supported
• TODO.md: Evaluated as low risk
• js/chromeExtensionApiAbstractions.js: Evaluated as low risk
• js/googleAnalytics.js: Evaluated as low risk

Comments suppressed due to low confidence (2)

src/google-analytics.js:121

• Ensure that the error object is a plain object before spreading it.

...error

src/google-analytics.js:103

• Handle network errors more gracefully in the fireEvent function.

console.error('Google Analytics request failed with an exception', e);

[Copilot]

Add a check to ensure that newSettings is not null or undefined before setting it in storage.

[Copilot]

The timestamp should be stored as a number instead of a string.

Suggested change

	timestamp: currentTimeInMs.toString()
	timestamp: currentTimeInMs

[0xdevalias]

const currentTimeInMs = Date.now(); contains a number, not a Date object; so calling .toString() on it isn't going to store the Date as a formatted string..

[0xdevalias]

Just wanted to make a quick update here.. have been pretty busy lately, but this has still been floating around in the back of my mind.

I'm thinking what I might do when I get a chance is do some quick 'sanity checks' on #20 in it's current state, and if that all works I will probably build/deploy an alpha/beta version of that to the Chrome Extension Store in the interim.. and then when I get some proper time to finish everything I want to do as part of that PR + test it properly I can make a proper release and deploy that as well.

Not sure when that will be (travelling at the moment), but wanted to note my plan here for everyone's info.

Originally posted by @0xdevalias in #21 (comment)

[0xdevalias]

Since I haven't had a chance to get back to working on this in ages, I just did a quick check that the main functionality in #20 seems to work; and then created a 2.0.0-alpha build of that + submitted it to the Chrome store.

I still intend to get back to finishing that PR 'properly' at some stage and getting it merged/etc; but at the very least, this should unblock the 'removed from the store because no MV3 version' blocker that currently exists from people being able to use the extension.

Originally posted by @0xdevalias in #13 (comment)