Reverting the changes causing release block

[Ayyanchira]

🔹 Jira Ticket(s) if any

• MOB-XXXX

✏️ Description

Please provide a brief description of what this pull request does.

[Copilot]

Pull Request Overview

This PR reverts changes that were previously causing a release block by modifying the GPG key import process and adjusting Gradle command flags for building and publishing.

• Reverts GPG key import steps to use a temporary file for importing the key instead of direct import
• Removes the verbose Gradle flags (--info and --build-cache) from build and publish commands
• Introduces the ORG_GRADLE_PROJECT_SIGNING_SECRET_KEY_RING_FILE environment variable in both the Build and Publish steps

Files not reviewed (1)

• maven-push.gradle: Language not supported

Comments suppressed due to low confidence (1)

.github/workflows/publish.yml:42

• Similar to the Build step, the Publish step references ~/.gnupg/secring.gpg which may not be generated by the revised GPG import process. Ensure that the key ring file exists at the specified location or adjust the import process accordingly.

ORG_GRADLE_PROJECT_SIGNING_SECRET_KEY_RING_FILE: ~/.gnupg/secring.gpg

[Copilot]

The environment variable ORG_GRADLE_PROJECT_SIGNING_SECRET_KEY_RING_FILE is set to ~/.gnupg/secring.gpg, but the new GPG import step does not create or ensure the existence of this file. Consider updating the GPG import process to either generate the expected key ring file or modifying the environment variable to match the actual file location.