Exclude slf4j-api from alloydb dependency to correct logging behaviour

[thongdk8]

Description

This PR addresses SLF4J dependency conflicts by excluding the slf4j-api module from the AlloyDB JDBC connector dependency (it is using v2 of slf4j-api while we are using v1.7 in our project). Without the exclusion, the logging behavior will not work correctly, especially in the Data Loader, and the Schema Loader will show a warning SLF4J(W): No SLF4J providers were found.

Related issues and/or PRs

NA

Changes made

• Exclude the slf4j-api module from the AlloyDB JDBC connector 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.
• I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
• 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)

NA

Release notes

Exclude slf4j-api from alloydb dependency to correct logging behaviour

[Copilot]

Pull Request Overview

This PR addresses SLF4J dependency conflicts by excluding the slf4j-api module from the AlloyDB JDBC connector dependency, ensuring consistent logging framework usage across the project.

• Added an exclusion block for slf4j-api to the AlloyDB JDBC connector dependency

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Torch3333]

LGTM, thank you!

[ypeckstadt]

LGTM. Thank you.

[komamitsu]

LGTM! 👍

[brfrn169]

LGTM! Thank you!

[feeblefakie]

LGTM! Thank you!