correct handling/publishing of gcp-common library

[havetisyan]

Description

Contribution Checklist:

• The pull request does not introduce any breaking changes
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

Attach Screenshots (Optional)

[gemini-code-assist]

Summary of Changes

Hello @havetisyan, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on correctly integrating and publishing the athenz-server-gcp-common library within the project's build and deployment pipeline. The changes ensure that this specific GCP-related common component is properly built, its dependencies are managed efficiently, and it is included in the automated publishing process, thereby making it available for other modules or projects that might depend on it.

Highlights

• GCP Common Library Publishing: The athenz-server-gcp-common library has been added to the publish.sh script, ensuring it is now properly deployed and published as part of the build process.
• Maven Module Integration: The libs/java/server_gcp_common module has been formally included in the root pom.xml, integrating it into the multi-module build structure of the project.
• GCP Common POM Refinements: The pom.xml for athenz-server-gcp-common has been updated to align with the latest parent version (1.12.25-SNAPSHOT), include a descriptive tag, and optimize its dependency declarations by reordering and adjusting scopes.
• Dependency Management Streamlining: The google-cloud-libraries-bom dependency management section has been removed from libs/java/syncer_common/pom.xml, simplifying the dependency resolution for the syncer_common module.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly integrates the athenz-server-gcp-common library into the build and publishing process. The changes include adding the new module to the main build, updating the publishing script, and cleaning up Maven POM files by removing a duplicate dependency and refactoring dependency management to be more modular. The changes are well-structured and correct. I have one suggestion to improve the maintainability of the publishing script.