Add parameter for the solo compatibility version

[rbarker-dev]

Problem

Right now the hiero-solo-action is configured to only run with a single version of solo. End users are locked into using solo at the current configured version in the action. If an user needs to use a different version of solo to pull in additional features, they will have to configure solo manually in their workflows to do this and the action becomes unusable.

Solution

We should add a parameter to enable the configuration of solo version dynamically in the action. Defaulting to solo latest.

Alternatives

No response

[hendrikebbers]

Until now the problem was that solo still changed that much from version to version that the commands how solo has been called were different. Once the CLI parameters of solo are stable we should add the suggested parameter. @jeromy-cannon is that already the case?

[jeromy-cannon]

Until now the problem was that solo still changed that much from version to version that the commands how solo has been called were different. Once the CLI parameters of solo are stable we should add the suggested parameter. @jeromy-cannon is that already the case?

No, the CLI parameters are not stable. We have a design, but we are still in the works of mapping the current CLI commands and flags over to the new design.