ci: Automated Release to Maven Central Repository using JReleaser

[SrinivasanTarget]

This pull request updates the publishing process for the project to use JReleaser and revises the corresponding documentation. The most important changes include modifying the GitHub Actions workflow to integrate JReleaser and updating the release guide to reflect the new publishing steps.

Workflow updates for JReleaser integration:

• .github/workflows/publish.yml: Replaced Maven-specific environment variables with JReleaser-specific variables and added a new jreleaserDeploy step to the workflow.

Documentation updates:

• docs/release.md: Updated the release guide to replace manual Sonatype Nexus steps with instructions for using the Maven Central Repository via JReleaser.

[Copilot]

Pull Request Overview

This PR replaces the manual Maven Central staging steps with an automated JReleaser workflow and updates the release documentation accordingly.

• Integrate JReleaser into the GitHub Actions pipeline (jreleaserDeploy step)
• Remove legacy Maven/PGP env vars and add JReleaser-specific secrets
• Revise docs/release.md to guide maintainers through the new publishing UI

Reviewed Changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.

File	Description
docs/release.md	Removed Sonatype Nexus steps and added instructions for central.sonatype.com
.github/workflows/publish.yml	Swapped Maven env vars for JReleaser env vars and added jreleaserDeploy

Comments suppressed due to low confidence (3)

.github/workflows/publish.yml:21

• [nitpick] The secret name for the GPG public key is 'SIGNING_PUBLIC_KEY' while the other JReleaser secrets use a 'JRELEASER_' prefix (e.g., JRELEASER_SIGNING_KEY). Consider renaming them consistently to avoid confusion.

          JRELEASER_GPG_PUBLIC_KEY: ${{ secrets.SIGNING_PUBLIC_KEY }}

.github/workflows/publish.yml:27

• [nitpick] Running both './gradlew publish' and './gradlew jreleaserDeploy' might be redundant since JReleaser can handle the full deployment. Consider removing the initial publish step or documenting why both are necessary.

          ./gradlew publish

docs/release.md:17

• [nitpick] The list numbering resets to '1.' after step 15, which may confuse readers. Consider using automatic markdown numbering or updating numbers sequentially for clarity.

1. Open [Maven Central Repository](https://central.sonatype.com/) in your browser.