Move kt_jvm[_lite]_proto_library targets into the BUILD file of the a…

…ssociated proto_library

To minimize the scope of this cleanup, alias targets are introduced in BUILD files that had incorrectly located kt_jvm[_lite]_proto_library targets.

This CL was generated using a script, and may have unusual names or target positioning as a result.

Metabug b/284050664

PiperOrigin-RevId: 710175849

src/frontends/sql/BUILD

@@ -20,6 +20,7 @@ load(
     "proto_library",
     "raksha_cc_proto_library",
 )
+load("//third_party/protobuf/build_defs:kt_jvm_proto_library.bzl", "kt_jvm_lite_proto_library", "kt_jvm_proto_library")
 
 package(
     features = ["layering_check"],
@@ -46,6 +47,28 @@ raksha_cc_proto_library(
     ],
 )
 
+kt_jvm_proto_library(
+    name = "sql_ir_kt_proto",
+    visibility = [
+        "//:__pkg__",
+        "//src/backends/policy_engine/abstract_interpretation:__pkg__",
+    ],
+    deps = [
+        ":sql_ir_proto",
+    ],
+)
+
+kt_jvm_lite_proto_library(
+    name = "sql_ir_kt_proto_lite",
+    visibility = [
+        "//:__pkg__",
+        "//src/backends/policy_engine/abstract_interpretation:__pkg__",
+    ],
+    deps = [
+        ":sql_ir_proto",
+    ],
+)
+
 cc_library(
     name = "decoder_context",
     srcs = ["decoder_context.cc"],