Support auto-upgrades for Linux and MacOS without dotnet

[jezzsantos]

This plugin (currently) requires that the CLI is installed using dotnet tool install automate --global on the machine where Rider is installed. Furthermore, in these early days of developing the plugin, the automate.exe CLI is evolving to support the plugin, and rapidly changing its external interfaces (specifically how it outputs its responses using --output-structured.

The plugin has been tested on both Windows and MacOS, as is able to work fine, when JB Rider is installed, and thus the dotnet CLI is installed in its default location. (see jezzsantos.automate.plugin.infrastructure.services.cli.OSPlatform).
In this configuration, the plugin can self-install the required automate.exe CLI, and keep it up to date with subsequent versions.

However, if the automate.exe is installed using any other method other than using the dotnet CLI, then its location on the local machine is not predictable to keep up to date. Even though the plugin allows the user to define the installation location.

Solution

For users (on Windows, Linux or macOS) who use a custom installation location, we need another strategy for updating the automate.exe CLI on their machine.

It may involve these things:

• elevated privileges
• another repository of the executables
• installation of the relevant dotnet runtime

At present these things are considered too hard to manage effectively.
We also don't know how many users have these outlier requirements on their machines.

The sole reason that the plugin is targetted at JB Rider only (at present), is that we can make a solid assumption that the dotnet CLI will be present on the machine. Whereas, with other JB IDEs (i.e. IntelliJ IDEA), that may not be a safe assumption.