Split java_lite_grpc_library from java_grpc_library Bazel rule

As discussed in #5237. This is already the direction the rule was going.

Before making the change, I need to get some agreement internally that the benefit outweighs the churn to our users. Otherwise I wouldn't be able to migrate existing usages.

There will need to be a long period where the new rule exists and you can still specify "flavor" for the old behavior, to allow migration.

CC @ceason

Start by reading the discussion in #5237 and confirming the internal agreement requested in this issue. Define the migration scope for a separate java_lite_grpc_library while retaining the old rule's flavor behavior long enough for existing usages to migrate.

Escrito por el modelo de indexación a partir del texto del issue.