fix(release): set gitPublish.username / password from env (real bot user)

[musketyr]

Summary

The 1.0.0.RC2 / RC3 retries reached :guide:gitPublishPush (so PR #23 + PR #24 did clear the previous blockers) but then crashed with:

fatal: could not read Username for 'https://github.com': No such device or address

gradle-git-publish:5.1.2 — pulled in by com.agorapulse.gradle.guide — dropped the legacy GRGIT_USER / GRGIT_PASS env vars and the -Dorg.ajoberstar.grgit.auth.username=... system property the old Kordamp-era workflow relied on. The v5 README is explicit:

If you relied on Grgit's authentication, such as GRGIT_USER, use the new username and password properties on the GitPublication.

This PR applies exactly the fix that landed on micronaut-rethrow at the 3.0.0.RC3 tag (commit 3ee67e9) — that's the rethrow tag that actually released end-to-end:

• docs/guide/guide.gradle — set credentials on the gitPublish extension directly, reading from GIT_PUBLISH_USERNAME / GIT_PUBLISH_PASSWORD env vars:

  gitPublish {
      username = providers.environmentVariable('GIT_PUBLISH_USERNAME').orElse('')
      password = providers.environmentVariable('GIT_PUBLISH_PASSWORD').orElse('')
  }

• .github/workflows/release.yml — pass agorapulse-bot as username and the existing AGORAPULSE_BOT_PERSONAL_TOKEN as password (standard GitHub HTTPS basic-auth). Drop the now-useless -Dorg.ajoberstar.grgit.auth.username=… flag. Qualify the task path to :guide:gitPublishPush so the gradle command matches the rethrow exemplar 1:1.

Test plan

• After merge, recreate the GitHub Release on the existing 1.0.0.RC3 tag (or cut 1.0.0.RC4) so the publishing workflow runs end-to-end.

🤖 Generated with Claude Code