[Feature]: Support Chrome channels and Chromium profiles

[ciltocruz]

Existing issues

• I searched existing issues and did not find a duplicate.

Problem or use case

Not everyone uses the stable Google Chrome release. When someone uses Chrome Beta, Chrome Dev, Chrome Canary, Chrome for Testing, or Chromium, those installations and their browser profiles should be available as cookie-import sources in Win-CodexBar. At present, the browser list does not expose these variants as distinct choices.

Proposed solution

Detect the Windows User Data directory for every supported Chrome channel and Chromium installation, and make each available as a separate cookie-import source while keeping existing Chrome and Microsoft Edge behavior intact.

Affected area

• Tray panel
• Settings UI
• Config file / settings persistence
• CLI
• Provider-specific behavior
• Installer / release packaging
• Startup / background behavior
• Documentation
• Other

Alternatives considered

No response

Visual details

No response

Additional context

Requested Windows User Data roots:

• Chrome: %LOCALAPPDATA%\Google\Chrome\User Data
• Chrome Beta: %LOCALAPPDATA%\Google\Chrome Beta\User Data
• Chrome Dev: %LOCALAPPDATA%\Google\Chrome Dev\User Data
• Chrome Canary: %LOCALAPPDATA%\Google\Chrome SxS\User Data
• Chrome for Testing: %LOCALAPPDATA%\Google\Chrome for Testing\User Data
• Chromium: %LOCALAPPDATA%\Chromium\User Data

[ciltocruz]

Implemented in PR #614 and ready for review.

The PR adds the requested Chrome Beta, Dev, Canary, Chrome for Testing, and Chromium cookie-import sources. The implementation is ready for review, so maintainers do not need to implement this request separately. Feedback is welcome.