Fix Gradle publish signing failure in release workflow

[Copilot]

The Publish Gradle Package job was failing in :signMavenJavaPublication because the signing key ID provided via workflow secret did not match the Gradle signing plugin’s required key-id format. This PR updates the workflow so Gradle signing relies on in-memory key material without forcing invalid key-id parsing.

• Root cause addressed

  • Removed SIGNING_KEY_ID from the publish-gradle job environment in .github/workflows/release-and-publish.yml.
  • Kept SIGNING_KEY and SIGNING_PASSWORD unchanged for in-memory signing.

• Why this unblocks publishing

  • Gradle no longer attempts to parse an invalid/masked key ID for signMavenJavaPublication.
  • Signing continues through the existing in-memory key path.

• Workflow delta (snippet)

  env:
    MAVEN_REPOSITORY_URL: ${{ secrets.MAVEN_REPOSITORY_URL }}
    MAVEN_USERNAME: ${{ secrets.MAVEN_USERNAME }}
    MAVEN_PASSWORD: ${{ secrets.MAVEN_PASSWORD }}
    SIGNING_KEY: ${{ secrets.SIGNING_KEY }}
    SIGNING_PASSWORD: ${{ secrets.SIGNING_PASSWORD }}

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Removes the SIGNING_KEY_ID secret from the release/publish GitHub Actions workflow environment.

Changes:

• Dropped SIGNING_KEY_ID from the job env passed into the release step.