fix: self-update operator early to ensure consistency

[merll]

📌 Summary

Updating the platform currently works in the following steps:

1. Update values otomi.version to new image tag
2. The operator starts to reconcile

• Team apps are deployed
• Pre-upgrade runs
• Operator detects it is out of sync with the version and updates itself (ArgoCD application)

3. The operator restarts and eventually completes the upgrade

This PR moves the version check above all other actions, making sure the operator image tag and ArgoCD application revision match the values. If an update has been made, it does not proceed but wait for its restart.

🔍 Reviewer Notes

Since the operator handles its own upgrade, only following changes benefit from this. For testing one needs to upgrade to this feature branch first, then on a following branch change the effect can be observed.

As a consequence, we would need to add this change to a patch release.

🧹 Checklist

• Code is readable, maintainable, and robust.
• Unit tests added/updated