1.13.0.0 "Going The Distance"

It's the first release of the 1.13.0.x cycle! Which may or may not be very long, depending on what fixes can be fit into a patch release. Yes, even before the first setup tool release, people had already found bugs in 1.13.0, but that means at least some of those are already fixed here! There aren't a ton of changes relative to 1.12.1.17, but there are some substantial ones.

• libGDX 1.13.0's Android backend at least temporarily depends on AndroidX. This adds the dependency to Android projects and sets the android.useAndroidX property to true.
• GWT 2.11.0 is used by the official libGDX 1.13.0.0 GWT backend now, so we only ever use the third-party backend if users select libGDX 1.12.1 (or maybe older).
• Construo has been updated to 1.4.2, which was a large amount of work that @fourlastor pulled off in a hurry! Despite relatively few files being changed in Construo itself, this was an interesting ordeal, but it allows Kotlin Android modules to coexist with LWJGL3 modules, and everything gets along now. Kotlin on iOS hasn't been tested yet, and I don't even know if that's something people do, but hopefully the fixes applied in Construo 1.4.2 are general enough that iOS will work regardless of languages.
• Graal Native won't cause problems on projects without an LWJGL3 module.
• Kotlin has been updated to 2.0.21. Tests using Kotlin should work now, if you have them.
• "Open in IDEA" works now with the current JetBrains Toolbox on Windows. JetBrains changed the name of a file that we need to open, and so all older Liftoff versions won't be able to "Open in Idea" with the current Toolbox. But this version works.

A known issue with 1.13.0 is that SpriteBatch is essentially broken on GWT (and only on GWT). It may work on TeaVM. You can use this substitute SpriteBatch as a dependency or by copying the file into your sources (the second way is the easier way). It probably doesn't perform as well as it should, but it isn't broken. If you don't target GWT, you should be unaffected by this.

This release, like the last one, does not include native builds for macOS; you should use the .jar download with a JDK (17 or greater) that you have installed. The .jar works everywhere as long as you have a JDK 17 or later installed. The Linux and Windows builds work on x64 architecture for those OSes, and don't need a separate JDK (which can be useful if Android Studio or IDEA is managing your JVM). Getting a macOS native .app to work is a serious hassle for users, involving a variety of command-line steps; see if the .jar is sufficient for you!

Thanks to @fourlastor , @Quillraven , and @nulldoubt (I hope I got the username right) for a variety of important contributions. And thanks to all the fearless early adopters of 1.13.0 who have been poking at this release to get it to work!