fix(ci): Remove duplicate GPG key import in release workflow

Remove manual GPG import step that was conflicting with setup-java's
built-in GPG handling. The duplicate import was causing exit code 2
errors during both setup and cleanup phases.

Now relies entirely on setup-java@v5's declarative gpg-private-key
and gpg-passphrase configuration for cleaner key management.

Fixes the "Failed to remove private key" error in GitHub Actions.

Author: schrepfler

.github/workflows/maven-publish.yml

@@ -24,13 +24,6 @@ jobs:
         server-password: MAVEN_PASSWORD                       # env variable for token in deploy
         gpg-private-key: ${{ secrets.OSSRH_GPG_SECRET_KEY }}  # Value of the GPG private key to import
         gpg-passphrase: MAVEN_GPG_PASSPHRASE                  # env variable for GPG private key passphrase
-#         settings-path: ${{ github.workspace }}              # location for the settings.xml file
-
-    - id: install-secret-key
-      name: Install gpg secret key
-      run: |
-        cat <(echo -e "${{ secrets.OSSRH_GPG_SECRET_KEY }}") | gpg --batch --import
-        gpg --list-secret-keys --keyid-format LONG
 
     - name: Publish package
       run: mvn --no-transfer-progress --batch-mode -DperformRelease=true clean deploy