fix(#509): add disable on current site control

[rbalogic]

Summary

This PR introduces a per-site disable control, allowing users to quickly turn ClearURLs off for the current site when it breaks a workflow.

It adds a popup action to toggle ClearURLs on the active site, persists the disabled hostnames in extension storage, and bypasses URL cleaning for requests and history updates originating from those sites.

Problem

Currently, ClearURLs can only be toggled globally. When a specific site breaks, users have no fast escape hatch other than disabling the entire add-on and waiting for a upstream fix. This makes site-specific regressions much more disruptive than necessary.

Changes

• Storage & State: Added a persisted disabledDomains list in extension storage.
• Background Script: Added shared hostname helpers and tab URL tracking.
• Popup UI: Added a new Site section featuring:
  • Current site status.
  • A toggle button (Disable on this site / Enable on this site).
• Logic Bypasses: - Bypasses webRequest URL cleaning when the current site is disabled.
  • Bypasses history API cleaning for disabled sites.
• i18n: Added English localization strings for the new popup UI elements.

Behavior

• Disabling a site strictly affects that specific site's hostname.
• The add-on remains active globally for all other sites.
• Users can easily re-enable the site using the same popup control.

Notes

• This PR is intentionally scoped to the per-site disable feature to address issue Add option to disable addon on current domain #509.
• It does not add an allowlist-only mode or a “clean only on selected sites” feature, as those would require separate product and implementation design.

[sonarqubecloud]

Quality Gate passed

Issues
26 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud