Change Software versions during restore of a lab.

[larslilja]

Problem Statement

Today you can do a backup of a topology with configuration, and restore it back to the same state, but if you want to "upgrade" your topology to the next release you can not easily do that today with the tool.

Please describe the problem to be addressed by the proposed feature.

Proposed Solution

I suggest that we add 2 flags to the restore task.

--contr_version

--edge_version

If the flags are not set, we will stick with the one in the yaml file.

The flags should do the normal version check, so we ensure that the software releases are available on the CML Cluster. As well as show which versions are there if the user types something wrong. Like we do in the deploy and add tasks. (Reuse if possible)

Please describe what you envision the solution to this problem would look like.

Alternatives Considered

Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and
tradeoffs being made.

Additional Context

Please provide any other information that may be relevant.