fix: exclude protobuf-javalite to resolve Bazel protobuf runtime conflicts

rocketmq-proto:2.1.2 transitively depends on grpc-protobuf-lite, which
pulls in protobuf-javalite. This artifact contains classes in the same
com.google.protobuf package as protobuf-java but with an incompatible
class hierarchy (GeneratedMessageLite vs GeneratedMessageV3). When both
jars are on the classpath, the wrong classes get loaded, causing:
- NoSuchMethodError: TimestampProto.getDescriptor() (lite has no descriptors)
- VerifyError: Duration not assignable to AbstractMessage (lite Duration
  extends GeneratedMessageLite, not AbstractMessage)

Maven pom.xml avoids this by excluding all transitive deps from
rocketmq-proto. Apply the equivalent in Bazel via excluded_artifacts.

Author: qianye1001

WORKSPACE

@@ -126,6 +126,9 @@ maven_install(
         "com.alibaba.fastjson2:fastjson2:2.0.59",
         "org.junit.jupiter:junit-jupiter-api:5.9.1",
     ],
+    excluded_artifacts = [
+        "com.google.protobuf:protobuf-javalite",
+    ],
     fetch_sources = False,
     repositories = [
         "https://repo1.maven.org/maven2",