Clean up dependencies

[Abacn]

• Delete it-splunk fork per TODO

• Do not attempt to shade test jar for v1 module

This resolves many warning logs like

[WARNING] Could not get tests for com.google.cloud.teleport.metadata:metadata:jar:1.0-SNAPSHOT:compile
Downloading from confluent: https://packages.confluent.io/maven/com/google/guava/guava/33.1.0-jre/guava-33.1.0-jre-tests.jar
Downloading from airlockRepo: https://us-maven.pkg.dev/artifact-foundry-prod/ah-3p-staging-maven/com/google/guava/guava/33.1.0-jre/guava-33.1.0-jre-tests.jar

and speeds up build as less 404

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.17%. Comparing base (bb033bc) to head (7fd56a0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #3600   +/-   ##
=========================================
  Coverage     52.17%   52.17%           
- Complexity     6054     6055    +1     
=========================================
  Files          1040     1040           
  Lines         63059    63059           
  Branches       6912     6912           
=========================================
  Hits          32902    32902           
  Misses        27926    27926           
  Partials       2231     2231           

Components	Coverage Δ
spanner-templates	72.10% <ø> (+<0.01%)	⬆️
spanner-import-export	68.75% <ø> (-0.03%)	⬇️
spanner-live-forward-migration	80.36% <ø> (ø)
spanner-live-reverse-replication	77.82% <ø> (+0.04%)	⬆️
spanner-bulk-migration	89.18% <ø> (ø)
gcs-spanner-dv	85.32% <ø> (ø)
see 6 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Summary of Changes

Hello, 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 cleans up the project by removing a temporary integration testing library fork that is no longer needed. Additionally, it adjusts the build configuration to stop attempting to shade test jars, which resolves recurring warning logs and speeds up the overall build process.

Highlights

• Dependency Cleanup: Removed the 'it-splunk' module and its associated source code, as it was a temporary fork intended for removal.
• Build Optimization: Disabled 'shadeTestJar' in the build configuration to resolve unnecessary 404 errors during dependency resolution and improve build performance.

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.

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. ↩