Feat: zulip:// URI Scheme for electron #470

[avijitdas126]

Added deep linking support with zulip://, registered the protocol handler, and implemented a dialog to choose between opening the link in the app or browser.

• Added deep linking functionality to open the app via custom protocol (zulip://).
• Registered the protocol handler using app.setAsDefaultProtocolClient("zulip").
• Implemented a dialog prompt to ask users whether to open the link in the desktop app or browser.
• Handled deep link routing in the main process to ensure smooth redirection.
• Fixed import issues related to electron/main and electron/common.

Fixes: #470

Platforms this PR was tested on:

• Windows
• macOS
• Linux (specify distro)

Self-review checklist

• Self-reviewed the changes for clarity and maintainability
  (variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

• Explains differences from previous plans (e.g., issue description).
• Highlights technical choices and bugs encountered.
• Calls out remaining decisions and concerns.
• Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

• Each commit is a coherent idea.
• Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

• Visual appearance of the changes.
• Responsiveness and internationalization.
• Strings and tooltips.
• End-to-end functionality of buttons, interactions and flows.
• Corner cases, error conditions, and easily imagined bugs.

[zulipbot]

Hello @avijitdas126, it seems like you have referenced #470 in your pull request description, but you have not referenced them in your commit message description(s). Referencing an issue in a commit message automatically closes the corresponding issue when the commit is merged, which makes the issue tracker easier to manage.

Please run git commit --amend in your command line client to amend your commit message description with Fixes #470..

An example of a correctly-formatted commit:

commit fabd5e450374c8dde65ec35f02140383940fe146
Author: zulipbot
Date:   Sat Mar 18 13:42:40 2017 -0700

    pull requests: Check PR commits reference when issue is referenced.

    Fixes #51.

To learn how to write a great commit message, please refer to our guide.

[avijitdas126]

@akashnimare could you please review this PR?

[andersk]

What are you expecting this to accomplish, in either case? Neither an Electron webContents nor an external web browser knows anything about zulip: URLs.

[avijitdas126]

What are you expecting this to accomplish, in either case? Neither an Electron

When a URL is received, the application presents a dialog to the user. If the user confirms (response.response === 0), the app sends an open-url event to the main window's webContents, allowing the app to handle the URL internally. If the user declines, the URL is opened in the default web browser using shell.openExternal(url).

[andersk]

Please don’t waste the time of open source maintainers with AI generated slop. If you don’t understand what’s going on well enough to see that this completely failed to address my question, then this is not the project for you.

[avijitdas126]

No sir, I cannot solve this issue using AI.I solved this issue using electron deeplinking documentation. When user hit zulip:// endpoint when open a dialog box if user want to open on the desktop click on open with desktop verify response.response===0 go to desktop using mainWindow.webContents.send("open-url", url); otherwise open with browser await shell.openExternal(url);