Add publish release workflow

[kazutoiris]

What is the purpose of the change

This pull request introduces a new workflow for automated release publishing. These changes will streamline release process and enhance the security and consistency of deployed artifacts.

Related issues/PRs

None.

Brief change log

• Added a new publish release workflow to automate the creation and deployment of releases.

  Details

  Pushing tags in the format 1.x.y will automatically generate a release with the title Apache Linkis Release-1.x.y in draft status.
  The generated release will include the following attachments:

  • apache-linkis-1.x.y-web-bin.tar.gz
  • apache-linkis-1.x.y-web-bin.tar.gz.asc
  • apache-linkis-1.x.y-web-bin.tar.gz.sha512
  • apache-linkis-1.x.y-bin.tar.gz
  • apache-linkis-1.x.y-bin.tar.gz.asc
  • apache-linkis-1.x.y-bin.tar.gz.sha512
  • apache-linkis-1.x.y-src.tar.gz
  • apache-linkis-1.x.y-src.tar.gz.asc
  • apache-linkis-1.x.y-src.tar.gz.sha512

• Upgraded maven-gpg-plugin version and configured pinentry mode for better handling of GPG signing in CI environments.

  Requirements for GitHub Action secrets configuration

  • MAVEN_GPG_PRIVATE_KEY: GPG private key in ASCII format
  • MAVEN_GPG_PASSPHRASE: Passphrase for the GPG key (if applicable)
  • OSS_SONATYPE_USERNAME: Username for Maven Central repository
  • OSS_SONATYPE_PASSWORD: Password for Maven Central repository

Checklist

• I have read the Contributing Guidelines on pull requests.
• I have explained the need for this PR and the problem it solves
• I have explained the changes or the new features added to this PR
• I have added tests corresponding to this change
• I have updated the documentation to reflect this change
• I have verified that this change is backward compatible (If not, please discuss on the Linkis mailing list first)
• If this is a code change: I have written unit tests to fully verify the new behavior.