Fix gRPC dependency issue

[brfrn169]

Description

We’ve recently been encountering the following errors in the ScalarDB Cluster tests:

java.lang.NoClassDefFoundError: io/grpc/internal/NoopSslSession
	at java.base/java.lang.Class.getDeclaringClass0(Native Method)
	at java.base/java.lang.Class.isTopLevelClass(Class.java:1693)
	at java.base/java.lang.Class.getSimpleBinaryName(Class.java:1678)
	at java.base/java.lang.Class.getSimpleName0(Class.java:1562)
	at java.base/java.lang.Class.getSimpleName(Class.java:1553)
	at io.grpc.netty.shaded.io.grpc.netty.ProtocolNegotiators$ProtocolNegotiationHandler.<init>(ProtocolNegotiators.java:1134)
	at io.grpc.netty.shaded.io.grpc.netty.ProtocolNegotiators$PlaintextHandler.<init>(ProtocolNegotiators.java:1056)
	at io.grpc.netty.shaded.io.grpc.netty.ProtocolNegotiators$PlaintextProtocolNegotiator.newHandler(ProtocolNegotiators.java:1039)
	at io.grpc.netty.shaded.io.grpc.netty.NettyClientTransport.start(NettyClientTransport.java:253)
	at io.grpc.internal.ForwardingConnectionClientTransport.start(ForwardingConnectionClientTransport.java:34)
	at io.grpc.internal.ForwardingConnectionClientTransport.start(ForwardingConnectionClientTransport.java:34)
	at io.grpc.internal.InternalSubchannel.startNewTransport(InternalSubchannel.java:271)
	at io.grpc.internal.InternalSubchannel.access$400(InternalSubchannel.java:68)
	at io.grpc.internal.InternalSubchannel$2.run(InternalSubchannel.java:213)
	at io.grpc.SynchronizationContext.drain(SynchronizationContext.java:96)
	at io.grpc.SynchronizationContext.execute(SynchronizationContext.java:128)
	at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:337)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

It appears that this issue is caused by the AlloyDB dependency recently added to ScalarDB Core in scalar-labs/scalardb#3029. The AlloyDB dependency introduces a conflicting gRPC dependency, which leads to the NoClassDefFoundError.

To resolve this issue, this PR excludes the AlloyDB dependency.

Related issues and/or PRs

N/A

Changes made

• Excluded the AlloyDB dependency.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

[Copilot]

Pull Request Overview

This PR fixes a gRPC dependency conflict issue by excluding the AlloyDB JDBC connector dependency across multiple build profiles in the ScalarDB Cluster project.

• Excludes com.google.cloud/alloydb-jdbc-connector from dependency declarations to resolve NoClassDefFoundError: io/grpc/internal/NoopSslSession
• Updates exclusion lists across three build profiles (default, cassandra, and cluster)
• Updates comment to reflect both netty and gRPC dependency issues

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[gemini-code-assist]

Summary of Changes

Hello @brfrn169, 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 aims to resolve a "java.lang.NoClassDefFoundError" that has been observed in ScalarDB Cluster tests. The error is caused by a gRPC dependency conflict, specifically introduced by the "com.google.cloud/alloydb-jdbc-connector" dependency. The solution involves updating the "project.clj" configuration to exclude the problematic AlloyDB dependency, thereby eliminating the conflict and restoring stability to the cluster tests.

Highlights

• Fixes gRPC Dependency Conflict: Resolves a "java.lang.NoClassDefFoundError" related to "io/grpc/internal/NoopSslSession" that was occurring in ScalarDB Cluster tests.
• Excludes AlloyDB Dependency: The root cause of the error was identified as a conflicting gRPC dependency introduced by the "com.google.cloud/alloydb-jdbc-connector". This pull request addresses the issue by explicitly excluding this dependency.
• Updates project.clj: The build configuration file "project.clj" has been modified to implement the dependency exclusion across relevant profiles.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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]

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.