- Increment the versions for AIShell application and the AIShell module.
- Update the check in AIShell module to look for PSReadLine v2.4.3-beta3 and above.
- Hide the `run_command_in_terminal` tool in macOS.
- Update the installation script to find the right PSReadLine dependency for a particular version of AIShell module.

…404)

Getting access token from Azure PowerShell fails with the error `"PowerShell did not return a valid response."`. This turns out to be an issue with the `Azure.Identity` library. After moving to the latest v1.14.2, it works again.

However, moving `Azure.Identity` to v1.14.2 causes a dependency conflict with the `Microsoft.ApplicationInsights.WorkerService` package, so this change also refactors the telemetry code a bit to depend on the  `Microsoft.ApplicationInsights` package instead, which is lightweight and much more appropriate for this application.

#403)

On macOS, when using the sidecar experience, `aish` cannot start local MCP servers and the `Azure` agent cannot get the access token from Az CLI.

This is due to the PATH environment variable not properly setup when iTerm2 starts `"aish --Channel ..."` in the new pane. iTerm2 uses `exec` to run the `aish` command, which directly execute the program without setting up the environment variables properly.

Because of that, the `az` and `pwsh` commands cannot be found when retrieving access token, and the MCP server commands cannot be found too, which caused local MCP servers to always fail to start.

The fix is to wrap it with `zsh` by `/bin/zsh -l -c "<aish-path> --channel <channel-string>"`. In this way, `zsh` will set up the environment properly, which will then be inherited by `aish`.

…408)

…tity credentials from Azure authentication flow (#412)

…Foundry Local (#413)

This PR contains the following 2 fixes:
1. Keep the original casing of the model's name for custom endpoint configuration.
2. Fix the error reporting to handle exception messages that already contains newline at the end.

OpenAI models require lower case for their names, but the custom endpoint may be case-sensitive, such as the endpoint set up by Foundry Local. So, we should keep the original casing for custom endpoint configurations.