Storage loading fix

[Zacgoose]

This pull request updates how configuration and branding data are accessed throughout the extension, ensuring that merged enterprise and local configuration is consistently retrieved from the background script rather than directly from storage. This improves reliability and maintainability, especially in environments with enterprise overrides. Additionally, the DetectionRulesManager is refactored to accept a ConfigManager instance, allowing it to use the same configuration retrieval logic.

Should fix: #122

[Copilot]

Pull request overview

This pull request refactors configuration and branding data access throughout the extension to consistently use merged enterprise and local configuration from the background script via message passing, rather than directly accessing storage. This ensures enterprise policy overrides are properly respected across all components.

Key changes:

• DetectionRulesManager now accepts a ConfigManager instance to use merged configuration
• Content script functions updated to request config/branding from background with fallback to local storage
• All changes follow a consistent error handling pattern with proper fallbacks

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
scripts/modules/detection-rules-manager.js	Added configManager parameter to constructor and updated loadConfiguration() to use ConfigManager when available for merged config access
scripts/background.js	Updated DetectionRulesManager instantiation to pass ConfigManager instance
scripts/content.js	Updated five functions (loadDeveloperConsoleLoggingSetting, showWarningBanner's fetchBranding, showValidBadge, sendCippReport, applyBrandingColors) to request config/branding from background via messaging with fallback to local storage

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.