Use Flink bazel artifacts for uploads (#344)

## Summary
Tested on the our clients side and we've fixed some things in the Flink bazel
deps which requires us to move off sbt.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [X] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated the stream processing job configuration to reference a
production-ready deployment artifact.
- Streamlined the artifact generation process with an improved build
mechanism for more robust deployments.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: piyush-zlai

api/py/ai/chronon/repo/run.py

@@ -132,7 +132,7 @@
 DATAPROC_ENTRY = "ai.chronon.integrations.cloud_gcp.DataprocSubmitter"
 ZIPLINE_ONLINE_JAR_DEFAULT = "cloud_gcp_lib_deploy.jar"
 ZIPLINE_ONLINE_CLASS_DEFAULT = "ai.chronon.integrations.cloud_gcp.GcpApiImpl"
-ZIPLINE_FLINK_JAR_DEFAULT = "flink-assembly-0.1.0-SNAPSHOT.jar"
+ZIPLINE_FLINK_JAR_DEFAULT = "flink_assembly_deploy.jar"
 ZIPLINE_DATAPROC_SUBMITTER_JAR = "cloud_gcp_submitter_deploy.jar"
 
 

distribution/build_and_upload_gcp_artifacts.sh

@@ -39,15 +39,15 @@ fi
 
 echo "Building jars"
 sbt clean
-sbt flink/assembly
 sbt service/assembly
 
 bazel build //cloud_gcp:cloud_gcp_lib_deploy.jar
 bazel build //cloud_gcp:cloud_gcp_submitter_deploy.jar
+bazel build //flink:flink_assembly_deploy.jar
 
 CLOUD_GCP_JAR="$CHRONON_ROOT_DIR/bazel-bin/cloud_gcp/cloud_gcp_lib_deploy.jar"
 CLOUD_GCP_SUBMITTER_JAR="$CHRONON_ROOT_DIR/bazel-bin/cloud_gcp/cloud_gcp_submitter_deploy.jar"
-FLINK_JAR="$CHRONON_ROOT_DIR/flink/target/scala-2.12/flink-assembly-0.1.0-SNAPSHOT.jar"
+FLINK_JAR="$CHRONON_ROOT_DIR/bazel-bin/flink/flink_assembly_deploy.jar"
 SERVICE_JAR="$CHRONON_ROOT_DIR/service/target/scala-2.12/service-0.1.0-SNAPSHOT.jar"
 
 if [ ! -f "$CLOUD_GCP_JAR" ]; then