Consider testing CodeQL also against Kotlin EA versions

**Description of the issue**

For some time now, all projects using Kotlin and CodeQL face the following situation:

1. A new Kotlin version is released
2. Dependabot, Renovate, or equivalent creates a PR to upgrade Kotlin
3. The PR fails as CodeQL doesn't support the new version yet
4. After some weeks, a CodeQL release is out for that version, but a new Kotlin version is also released briefly after, which basically restarts the process from step 1

The reported cases since last October:
* https://github.com/github/codeql/issues/22189
* https://github.com/github/codeql/issues/22210
* https://github.com/github/codeql/issues/21938
* https://github.com/github/codeql/issues/21484
* https://github.com/github/codeql/issues/21345
* https://github.com/github/codeql/issues/20661

Just by looking at the timeline of some of these issues, it should be visible how many public projects keep the Kotlin upgrade on hold due to the CodeQL compatibility.

Would you consider testing the current CodeQL version against the [Kotlin early-access versions](https://kotlinlang.org/docs/eap.html)?

I understand testing against EA versions won't necessarily mean anticipating the necessary changes, but I wonder if something relatively cheap could be achieved with a GitHub Actions matrix to at least bring awareness to the process.

Start by reviewing the reported CodeQL issues and the Kotlin early-access version documentation, then inspect the repository's existing GitHub Actions workflows for Kotlin version testing. Determine whether a matrix can test current CodeQL against Kotlin EAP releases and define how failures should surface. Done means the approach is documented or implemented with maintainable coverage for EAP versions.

Written by the indexing model from the issue text.