Adding the `/kusto` command in copilot-cli

### Describe the feature or problem you'd like to solve

I am a Microsoft employee and the most tedious work for me would be analysing kusto logs and give me a visual and clear understanding of going through the logs about the issue

### Proposed solution

Here is the suggested approach:
1. As a user, if you entered the command say `agency copilot` now after this we generally enter the command as `/login`, in this based on whether the user has logged in from enterprise github account we should give the user the option for an additional command to perform i.e `/kusto`.
2. As soon as the user after successful login types in a command `/kusto` it is going to ask the user to enter the code which is sent over to them on the authenticator app (an approach which could be followed for 2MFA authentication to ensure better security.
3. Once, both the steps are done, the user needs to enter the connection URL in there, as soon as user is prompted to enter this, the connection to that particular cluster has started.
4. Next up, user could enter the database name once the connection is established (for this we could show the option to select the database) also.
5. Once the table is collected the next step is about righting the KQL query - since different teams might be using different type of query, the user could enter in the query (once the user has entered this should be stored as a boilerplate in the memory if this is possible, so that they dont have to add this query every time).
6. As soon as the query is being entered, then corresponding to this all sorts of authentication and authorization will be performed in the background, all the queries would be thoroughly analysed for the root cause analysis (if any) and stack trace and failure message along with code could be shown as output to the user.
7. In case the user wants to see a more detailed report, then we could add the link for go to Azure Data Explorer for more descriptive details

Note: I am suggesting this feature based on my experience, with the difficulty I feel with analysing the logs going through them one by one, where all other tasks are getting automated, if this task could be automated or atleast could reduce the bit of work, It would be of great help.
Please reach to me on Teams here is my alias: `mochauhan`

### Example prompts or workflows

_No response_

### Additional context

_No response_