The cn1:gamebuilder goal resolves the editor as
com.codenameone:codenameone-gamebuilder:<pluginVersion>:jar-with-dependencies
from Maven Central, but that artifact was never published, so the goal
failed on every released version (issue #5292). The core/plugin/archetype
release itself is unaffected.

The editor lives outside the maven/ reactor (scripts/gamebuilder), compiles
at Java 17, and depends on the core/javase/plugin built in the reactor, so it
could not simply be added as a reactor module. Four gaps are closed:

- scripts/gamebuilder/pom.xml: new gamebuilder-central profile (inherited by
  the common + javase modules) reproducing maven/pom.xml's Central plumbing --
  source + javadoc jars, GPG signatures and the central-publishing bundle.
  Off by default so dev builds are unaffected.
- maven/update-version.sh: version-syncs the gamebuilder module and the
  cn1.version/cn1.plugin.version it builds against to the release version, so
  the published artifact matches the plugin version the goal resolves. Uses
  perl rather than versions:set because the old SNAPSHOT plugin is not
  resolvable in a clean CI .m2 at that point.
- release-on-maven-central.yml: after the core release succeeds, a second
  JDK-17 pass builds and deploys the editor to Central, plus an informational
  confirm poll.
- maven/pom.xml: removed the dead, never-functional gamebuilder-release
  profile (its documented command would re-deploy the released reactor and
  ship unsigned artifacts) and corrected a stale comment in the javase pom.

Verified locally on JDK 17 that the build produces the editor's
jar-with-dependencies plus sources/javadoc for both modules. GPG signing and
the Central upload mirror the proven main-reactor config and are exercised by
the next tagged release.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>