Proto fetching release problems

[GabyUnalaq]

Description

The current implementation of the Python SDK uses the ankaios version and fetches the proto files from that specific release. This has proved to work fine in the production part, where everything is released, but during development, if ankaios is not yet released, and the proto files have been updated, then working on the same feature on this side is a hassle due to manually needing to update the proto files, both in testing the feature and running the examples.

For this, we need a solution that needs to:

• lead to easier development cycle for the control interface enhancements
• provide the proto files for the prod mode as well, similar to how it's working now

Goals

The proto files situation is handled more efficiently and suits both production and development.

Ideas / pros and cons

This section aims to bring all the ideas into a pros and cons table. Please modify directly the table if you consider additional factors or ideas.

Method	Dev friendly	No duplicated protos
Fetch from release only	🚫	✅
Copy paste the protos	✅	🚫
Fetch from a version / branch	✅	✅
Fetch from the released api	✅	✅

Final result

Summary

To be filled when the final solution is sketched.

[GabyUnalaq]

The current solution implemented by #89 is the following:
If the ankaios version has the pre ending, then the protos should be fetched from the main branch of ankaios, not the release. This fixes the proto problems from before a release, but during the development, while the proto changes are on a different branch, the problem persists. There are 2 solutions here:

• Commit and merge the proto changes in main before actually working at the full feature, so that they are available (I am not sure it's worth it, the protos might change again during development and the code will need to be stabilized before merge eitherway);
• Keep manually updating the proto files when working locally to the sdk (the ankaios examples will work by specifying the branch, but locally, the user will need to manually update the protos and regenerate the pb2 files).