fix: Better UX for expired PAT for Gist publishing ISSUE #1549

[jayzalani]

Added setWarningDialogToSetting to Implement Navigation for the Settings Button in Warning Dialog

Description:
This PR addresses [ISSUE #1549] by introducing a new function, setWarningDialogToSetting, which enhances the warning dialog by adding navigation to the Settings button.

Changes Implemented:

1. Added setWarningDialogToSetting function to handle the navigation logic.
2. Retained the existing showWarningDialog, ensuring backward compatibility.
3. Implemented unit tests to validate the new functionality.
4. Provided a video demonstration showcasing the functionality in action.

Why This Change?
The previous implementation (showWarningDialog) did not support navigating to the settings page when users encountered a warning. Instead of modifying/removing it (to avoid breaking existing functionality), I introduced a new function to handle this scenario efficiently.

Demo:
https://github.com/user-attachments/assets/6b66fefc-dad6-4729-b04e-58ef410671e8

I think these would greatly help Improving users Experience as user not have to waste 30-40minutes figuring out what went wrong when PAT expires I also wrote small message for user in Dialogue box "Your GitHub Tokens might have expired!" making him go and check the settings page 😊

[codebytere]

Hey @jayzalani, while we appreciate you trying to contribute, the quality of this PR doesn't meet our standards for a few reasons, including:

• Changing code with no clear benefit
• Arbitrary unrelated additions to package lock.

Based on these oddities and a few other quirks, we suspect this PR of being entirely AI-generated. While Electron appreciates and encourages community contributions, its maintainers only have limited bandwidth. AI-generated PRs will not be reviewed and will be closed as invalid.

This PR will now be closed. In the future, raising more PRs with purely AI generated content will result in a organization level ban. Please read our GSoC 2025 contributor guidance, specifically the section on "Project Contributions" and subsection 4.

[jayzalani]

ok no problem I will keep in mind and will contribute as per rules @codebytere 😊