rules_proto_grpc_java's maven.install should use default "maven" name

[ejona86]

Issue Description

Since the dependencies in maven.install are intended to be part of the user's binaries, they need to participate in the global version selection process. Otherwise users will have multiple versions of protobuf/grpc-java in their classpath. 26f537b introduced the problem.

This happened in grpc/grpc-java#12149 and was resolved by avoiding the rules in rules_proto_grpc_java that use rules_proto_grpc_java_maven

CC @daniel-b2c2, @aaliddell

Log Output

rules_proto_grpc Version

5.2.0

Bazel Version

??

OS

Linux

Link to Demo Repo

No response

MODULE.bazel or WORKSPACE Content

BUILD Content

Proto Content

Any Other Content

[aaliddell]

Is there a definitive position for which way is correct? I changed it to be not maven because that was causing issues previously. I can change it back but we are then liable to get version skew if a user specifies a different version of grpc-java etc in the root module, as the protoc plugin will not be in line. Whether or not this is problematic depends on the way the skew goes...

[aaliddell]

Changed in 5.4.0 release