You can look at this FAQ - we explain how Kubernetes upgrades are managed.
“The Qovery team manages your Kubernetes cluster’s upgrade; you don’t have to think about it. Upgrades from one minor Kubernetes version to another require a good amount of tests to make sure everything goes smoothly with zero interruptions for your app. This is why Qovery always provides 1 or 2 minor versions below the last one offered by the cloud provider. Our goal is to guarantee you the maximum uptime.”
So you have two options here:
Create a new cluster via Qovery and move your apps on this new cluster;
Wait for Qovery to support its support for 1.24 BUT in the meantime as you experienced, you won’t be able to update your cluster;
We are working on a version of Qovery where you can manage your Kubernetes upgrades yourself. It will be up to you;
We will update our FAQ and error message to explicitly state more clearly than you should not changed any resources managed by Qovery on Provider side (managed DB types, cluster version, etc). If you need to, we will add the support for it and help you with that, but it needs to be done via Qovery.