Description

This PR introduces support for highlighting domains in the Masked Domain List (MDL) that are subject to script blocking. It decouples script blocking logic from IP protection and adds a visual indicator when loaded scripts or iframes originate from domains listed in the MDL with specific blocking actions.

Relevant Technical Choices

• Added a new side menu item and icon specifically for script blocking, separating it from IP Protection.
• Created a dedicated page to list domains involved in script blocking using data from the MDL.
• Filtered the MDL entries to only show rows where the third column indicates “Entire Domain Blocked” or “Some URLs are Blocked.”
• Implemented logic to track domains from which active content (scripts, iframes) is loaded in the service worker.
• Hooked into the service worker to listen for relevant network activity and send data to the provider.
• Enabled sending of script blocking data to devtools panels
• Matched response domains against the MDL to identify and highlight blocked sources.
• Introduced a new provider to store and manage script-blocking-related state across the extension.
• Updated the MDL table structure and added flags to indicate which blocked domains were actually seen during the session.

Testing Instructions

Additional Information:

Example websites blocked in MDL

• https://customfingerprints.bablosoft.com/
• https://lab.alpineiq.com/
• https://app.push-ad.com/

Example of MDL
content.24ttl.stream

Screenshot/Screencast

Checklist

• I have thoroughly tested this code to the best of my abilities.
• I have reviewed the code myself before requesting a review.
• This code is covered by unit tests to verify that it works as intended.
• The QA of this PR is done by a member of the QA team (to be checked by QA).

Fixes #