Add custom commands to open Kusto servers in Kusto Explorer

[MattKotsenas]

Description

Kusto has two "Kusto Explorer" apps for viewing and querying data:

• One is a Windows-only ClickOnce app
• One is a web-based client

Both are popular with different audiences. This change adds both to the actions list for the cluster resource. I can also add the commands to database resources, but I thought that might be cluttering for most users.

Contributes to #8233

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12609

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12609"

[MattKotsenas]

I'm not sure how best to test this scenario (if required) so feedback welcome in that area.

[MattKotsenas]

Here's a snapshot from the Playground app

[Copilot]

Pull Request Overview

This PR adds custom commands to Azure Kusto (Azure Data Explorer) resources that allow users to open the Kusto Explorer tools directly from the Aspire dashboard. The feature provides two commands: one to launch the desktop Kusto Explorer (Windows-only) and another to launch the web-based Kusto Explorer.

• Adds two new resource commands for opening Kusto Explorer (Desktop and Web versions)
• Implements platform-specific command visibility (Desktop command hidden on non-Windows platforms)
• Adds fallback interaction dialog when web explorer fails to launch automatically

[davidfowl]

Why is it a command vs being an additional URL?

[MattKotsenas]

I went this route for two reasons:

1. It uses the "official" tool launcher that Kusto provides, and was suggested by the Kusto team
2. It bypasses any potential port shenanigans; if you do any kind of port forwarding for the local scenario, this way will definitely see the client-side port and use it correctly. (I've not personally run into this myself)

Let me know what you think or what your concerns are and I'm happy to adjust.

[MattKotsenas]

Also to provide more context:

For deployed clusters, you currently can click on the URL and you'll get redirected to the web explorer. So I could just add the desktop app as a command. Adding both was more for discovery and parity.