Update to MV3 (and other updates)

Summary:
- Prevents memory leaks
- Improves optimization
- Better handles edge cases

Critical Bug Fixes & Stability

Fixed several critical race conditions (v1.44.0-1.44.3) where the extension failed to check for active sub-frames (iframes). This fundamental flaw caused global data (Cache, Service Workers) and container data to be cleared prematurely, even when still in use by another tab. The active-domain checks are now robust, sub-frame aware, and correctly handle edge cases, preventing data from being destroyed.

Made the "Force Clear" feature (v1.44.4) safer. It now checks all dependencies (like scripts and frames) individually before deleting, preventing it from clearing data used by other unrelated tabs.

Addressed startup race conditions (v1.44.4) to ensure correct fail-safe settings and proper dependency restoration on browser launch, preventing momentary malfunctions.

Performance Optimizations

Significantly improved data clearing speed by batching API calls (v1.44.1). Instead of clearing 50 hosts with 100+ separate, slow API calls, the extension now groups them into just a few parallel operations.

Massively improved UI responsiveness by using DocumentFragment (v1.44.0, v1.44.4). This prevents the Options page and Popup from freezing when rendering lists for users with hundreds of rules.

Optimized "Deep Clear" (v1.44.0) to scan cookies in parallel and stopped unnecessary session saving (v1.44.4) to reduce disk writes when the startup-clear feature is disabled.

Other Key Improvements

• Fixed a UI bug in the popup (v1.44.0) where the status text would not update immediately after saving changes.
• Improved tab-refresh logic (v1.44.4) to correctly refresh tabs if one of their sub-frames (not just the main frame) was cleared.
• Added support for IPv6 literals (v1.44.0).
• Removed redundant code and translated all internal console logs to English for consistency.