[GSK-1813] Fix giskard server upgrade runs for 20mns without returning

[Inokinoki]

Description

Our latest image could disappear (or not on the first 10 items in Docker Hub repository), where the client will get stuck on parsing.
Use the version matching the local Giskard client in this case, and handle a few edge cases during upgrade.

Related Issue

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[linear]

GSK-1813 Giskard server upgrade runs for 20mns without returning any logs

Discovered during user test with Maximilien (unifai). Comments from weixuan :

Yes, I also encountered in the demo instance. It got stuck somewhere as we discussed during the meeting yesterday. As a workaround, I modified the version in the config file under $GISKARD_HOME.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication