Confusion about supported Kubernetes versions

/kind bug

**1. What `kops` version are you running? The command `kops version`, will display
this information.**
git-v1.33.0

**2. What Kubernetes version are you running? `kubectl version` will print the
version if a cluster is running or provide the Kubernetes version specified as
a `kops` flag.**

v1.32.6

**3. What cloud provider are you using?**

AWS

**4. What commands did you run? What is the simplest way to reproduce this issue?**

kops upgrade cluster --name XXXXX

**5. What happened after the commands executed?**

kops said:
```
W0826 12:16:37.623873 3025 upgrade_cluster.go:207] cluster version "1.32.6" is greater than the desired version "1.32.4"

No upgrade required
```
**6. What did you expect to happen?**

I expected kops to suggest upgrading to Kubernetes 1.33.4 (because kops is v1.33 so it should support Kubernetes 1.33, right?) or at least to 1.32.8 as the latest patch release of the Kubernetes version installed in the cluster. But why is 1.32.4 "the desired version" and by whom is it desired?

**7. Please provide your cluster manifest.**

Irrelevant

**8. Please run the commands with most verbose logging by adding the `-v 10` flag.
Paste the logs into this report, or in a gist and provide the gist link here.**

[t.txt](https://github.com/user-attachments/files/21981072/t.txt)

**9. Anything else do we need to know?**

You see, I rely on https://kubernetes.io/releases/ to find out the latest Kubernetes versions, and so does our security team, and I am very much surprised that kOps has its own idea of "desired" versions. If kops takes its supported versions from https://github.com/kubernetes/kops/blob/master/channels/stable then probably this file is outdated or something?

Start with the kops upgrade cluster command and the referenced channels/stable file, then review the attached verbose log t.txt to trace why Kubernetes 1.32.4 is treated as the desired version. Compare that behavior with the reported Kubernetes 1.32.6 and 1.33.4 expectations. Done means the supported-version source and desired-version behavior are clear and match the documented or intended policy.

Written by the indexing model from the issue text.