Migrating Chrome Extension to Manifest V3

[DanazSdiq]

Related Ticket/PR

• Epic ticket
• Jira ticket

Changes

This PR migrates the Chrome extension to manifest V3. Most likely, we have to maintain different listeners for Chrome and Firefox versions of the extension because service workers are still not implemented in Firefox. To minimize the hassle of handling these discrepancies, I have extracted these handlers into reusable pieces of code that can be injected to Firefox's event listeners with little to no changes (those changes are yet to be made).

The most important change when migrating to manifest V3 is introducing daemon/initOverload.js script. In basic terms, daemon/initOverload is where we have access to both chrome.runtime and window. This allows us to communicate to and from the worker to the outside of the worker, which is where we essentially handle ads.

Requirements Before Merging

• New users (users without an account) are redirected to the results page upon installing the extension
• Making sure a user can create an account and that the token is present in both the results FE and the extension
• Rawlogs are properly captured while browsing FB
• Check if users are prompted again for permissions when installing the extension

[DanazSdiq]

I realized that I have not taken the backward compatibility of userData.isNotifiedUser into account. I changed the value of that attribute from string to boolean. Let's not merge this until I investigate that a bit further