fixed upgrade from 2.5.x to 2.6.x, by first upgrading the mixcoord

[nustiueudinastea]

fixed upgrade from 2.5.x to 2.6.x, by first upgrading the mixcoord, before deploying the streaming node. streaming node needs 2.6.x before it can become healthy.

Haven't fully tested this but want to get your feedback on this. Do you think this is the real issue?

This PR tries to fix #446

If you think this is the right approach I will fix the DCO and anything else that might need fixing.

[sre-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nustiueudinastea
To complete the pull request process, please assign alintalu after the PR has been reviewed.
You can assign the PR to them by writing /assign @alintalu in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.57%. Comparing base (a961596) to head (41094cf).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #447   +/-   ##
=======================================
  Coverage   76.57%   76.57%           
=======================================
  Files          65       65           
  Lines        6029     6029           
=======================================
  Hits         4617     4617           
  Misses       1159     1159           
  Partials      253      253           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.