Re-initialize on Base64 Config Change

[ibolton336]

When the Base64-encoded configuration (or its decoded content) changes, we want to detect and re-initialize the extension to ensure new config values take effect immediately.

---

Tasks

1. Implement Change Detection

   • Monitor the Base64-encoded config in real time or at key points (e.g., on save, on profile switch, etc.).
   • Compare the new value with the old cached value to detect changes.

2. Trigger Re-initialization

   • If the new config is different, programmatically re-initialize the necessary extension states:
     • Reload analysis
     • Refresh webview content
     • Re-parse rules
   • Ensure minimal disruption to the user (i.e., avoid a full extension reload if possible).

3. Update Event Flow

   • Integrate this logic into any existing config update functions or watchers.
   • Make sure that when the user updates the configuration (via UI/webview or VS Code settings), the event triggers the re-init.

4. Testing & Validation

   • Verify that all extension functionalities (e.g., analysis, status bar commands) still work as expected after a re-init.
   • Test edge cases, such as:
     • Multiple quick successive changes to the config
     • User reverting to a previous configuration

---

Acceptance Criteria

• Config changes are detected reliably.
• Extension refreshes to adopt new config with minimal user interruption.
• No stale state remains after re-init.