chore: Refactor GPG handling in GitHub Actions workflow

- Moved the setting of GPG_TTY to the build command to ensure proper environment variable handling during deployment.
- Removed the separate GPG_TTY setup step to streamline the workflow.
- Maintained the overall efficiency and clarity of GPG key management in the deployment process.

Author: Marvin Zhang

.github/workflows/publish.yml

@@ -78,14 +78,13 @@ jobs:
         env:
           GPG_PRIVATE_KEY: ${{ secrets.GPG_PRIVATE_KEY }}
 
-      - name: Set GPG_TTY
-        run: export GPG_TTY=$(tty)
-
       - name: Reload gpg-agent
         run: gpg-connect-agent reloadagent /bye
 
       - name: Build and Test
         run: mvn clean test
 
       - name: Build and Publish to Maven Central and GitHub Packages
-        run: mvn clean deploy -P ossrh,github -Dgpg.passphrase=${{ secrets.GPG_PASSPHRASE }}
+        run: |
+          export GPG_TTY=$(tty)
+          mvn clean deploy -P ossrh,github -Dgpg.passphrase=${{ secrets.GPG_PASSPHRASE }}