Update Maven Central coordinates to "org.korge" and switch publishing to vanniktech plugin

[jobe-m]

No description provided.

[augmentcode]

🤖 Augment PR Summary

Summary: Migrates KorGE’s Maven/Gradle coordinates to the org.korge.* namespace and replaces the bespoke Sonatype OSSRH staging/release logic with the com.vanniktech.maven.publish plugin targeting the Central Portal.

Changes:

• Updates group IDs and Gradle plugin IDs (engine/library/settings/kproject) and adjusts E2E builds to consume the new coordinates.
• Reworks publishing setup in BuildSrc and plugin modules to use mavenPublishing (including richer POM metadata).
• Removes legacy Sonatype REST automation (start/close/promote) and OSSRH snapshot repository references.
• Updates CI publishing workflow to run publishToMavenCentral with Central Portal credentials and in-memory signing key env vars.
• Refreshes various dependency/tool versions and updates Gradle wrappers in E2E projects.

Technical Notes: Adds the Central Portal snapshots repository (https://central.sonatype.com/repository/maven-snapshots) to multiple builds to support resolving/publishing snapshot artifacts.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 4 suggestions posted.

Comment augment review to trigger a new review at any time.

[malliaridis]

I went over the changes and it looks quite a lot of work for renaming and configuring a new plugin for publishing. I think there is much to improve here over time.

Once this is done I would recommend moving the gradle plugins into separate repo, as they are not mandatory for KorGE nor do they have anything in common. If they are providing useful stuff for the korge repo or consumers and have to be published for this reason, they should in my opinion follow their own release cycle. This would also decouple korge from gradle plugins and simplify a lot the overall gradle config stuff. Additionally:

• I'd change the URL in the license from master branch to main, as there is no master branch in the project and it is just an alias for main

I haven't tried it out yet, nor have I searched the project for other references of the old namespace (plan to do that). But what will be very important is

• Add to the README the namespace change, as this is a breaking change and most consumers will have to update their imports.

I would even recommend creating a major release because of that, but if it is well documented, perhaps we can also allow a minor release.

[jobe-m]

I went over the changes and it looks quite a lot of work for renaming and configuring a new plugin for publishing. I think there is much to improve here over time.

Once this is done I would recommend moving the gradle plugins into separate repo, as they are not mandatory for KorGE nor do they have anything in common. If they are providing useful stuff for the korge repo or consumers and have to be published for this reason, they should in my opinion follow their own release cycle. This would also decouple korge from gradle plugins and simplify a lot the overall gradle config stuff. Additionally:

Yes, that is an good idea. I would do this in separate PRs later.

I would even recommend creating a major release because of that, but if it is well documented, perhaps we can also allow a minor release.

Fully agree. Let's work on main branch towards release 7.0.0

[augmentcode]

Review completed. 4 suggestions posted.

Comment augment review to trigger a new review at any time.

[jobe-m]

Checked with publishing SNAPSHOT-release to MavenLocal, building and testing my korge-fleks based game application. Looks fine.