Add feature to disable --experimental_java_proto_library_enforce_strict_deps for

non-compliant packages that depend on java_x_proto_library targets. This will enable blaze
to enforce strict_deps by default while missing dependencies are added to these packages.

Changes made using newly released blaze flag:
  USE_CANARY_BLAZE=nightly blaze build -k --experimental_java_proto_library_enforce_strict_deps

then extracting the packages from the resulting add_dep commands, and for each package running:
buildozer 'add features -jpl_strict_deps' <package>:__pkg__

More information: []

Tested:
    TAP sample presubmit queue
    []

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=206349847

java/google/registry/dns/BUILD

@@ -3,6 +3,7 @@
 
 package(
     default_visibility = ["//visibility:public"],
+    features = ["-jpl_strict_deps"],
 )
 
 licenses(["notice"])  # Apache 2.0

java/google/registry/tools/BUILD

@@ -1,5 +1,6 @@
 package(
     default_visibility = ["//visibility:public"],
+    features = ["-jpl_strict_deps"],
 )
 
 licenses(["notice"])  # Apache 2.0