Add a new workflow for publishing new versions

[MertNYuksel]

Add a new workflow that publishes new releases.

Remove the code that reads these secrets from the local.properties file. This will prevent or at least make it harder for developers to publish new versions from their development machines

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

"The 'publish' workflow is triggered on new releases. It sets up an environment, runs unit tests, and publishes the new version of the library by invoking 'publish' on Gradle. In the final step, we retrieve credentials and signing info from GitHub secrets, set them as environment variables. The 'publish-root.gradle' then uses these environment variables to publish the new release."

Motivation and Context

I want to automate publish new version process.

How Has This Been Tested?

I tested using Act.

Screenshots (if appropriate):

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.