[ENHANCEMENT] Manual Re-enablement of Disabled Email Channels

**Description:**
Currently, if a user's email notification channel is disabled on our side (e.g., due to repeated delivery failures) but is still marked as verified by GitHub, the `SyncUserProfileInfo` function will automatically re-enable it during the next sync. While this ensures consistency with GitHub's verified status, it bypasses any manual intervention or user-initiated re-enablement process.

We need a mechanism for users to manually re-enable their email notification channels that have been disabled by the system, even if GitHub still reports them as verified. This would provide users with more control over their notification preferences and allow for a more nuanced handling of disabled channels.

**Acceptance Criteria:**
- Users can view the status of their email notification channels, including whether they are disabled by the system.
- Users have a clear way to initiate the re-enablement of a system-disabled email channel.
- The re-enablement process should ideally include a verification step (e.g., sending a confirmation email) to ensure the user still has access to the email address.
- The `SyncUserProfileInfo` function should be updated to respect a user's manual re-enablement choice, potentially by not automatically re-enabling a channel that was manually disabled by the user.

**Future Considerations:**
- Explore options for integrating with GitHub's email verification status more deeply to avoid conflicts.
- Consider UI/UX implications for presenting disabled channels and re-enablement options.