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.

Commencez par examiner les problèmes CodeQL signalés et la documentation des versions Kotlin en accès anticipé, puis inspectez les workflows GitHub Actions existants du dépôt pour tester les versions de Kotlin. Déterminez si une matrice peut tester la version actuelle de CodeQL avec les versions EAP de Kotlin et définissez comment les échecs doivent être signalés. Le travail est considéré comme terminé lorsque l’approche est documentée ou implémentée avec une couverture maintenable des versions EAP.

Rédigé par le modèle d'indexation à partir du texte de l'issue.