Remove java_tools_javac14 (releases and dependencies) from Bazel.

Java_tools_javac14 is a binary equivalent to java_tools_javac11. It was split from java_tools_javac 11 in order to be able to provide specific support for Java 14.

As a result a release of java_tools_javac* we now need 6 binaries and fix of dependencies and their hashes in Bazel on cca. 18 different places. Adding another Java version (e.g. Java 15) will add additional 3 binaries and 9 places to fix (total 9/27).

Also JDK 14 has reached EOL.

It makes sense to have only one release until we actually have some specific support for Java 14 or newer.

This is a partial revert of commits fe291f7dcadc20eb85cff07b2cd4d899d79fba71 and 693c88a8f897b6764b98c7d9da922ffc96c6d890:
- Add support for toolchain java 14
- Add unit test against released java_tools_javac14

Closes #12180.

PiperOrigin-RevId: 334346567

src/BUILD

diff --git a/src/BUILD b/src/BUILD
index 2cb0b5b..5bbf5c3 100644
--- a/src/BUILD
+++ b/src/BUILD
@@ -570,9 +570,7 @@
     "//conditions:default": [],
 })
 
-JAVA_VERSIONS = ("11", "14")
-
-# TODO(davido): Hard code the javac 11 for now; it is required for default toolchain.
+JAVA_VERSIONS = ("11",)
 
 [
     genrule(
@@ -763,9 +761,6 @@
         "@remote_java_tools_javac11_test_darwin//:WORKSPACE",
         "@remote_java_tools_javac11_test_linux//:WORKSPACE",
         "@remote_java_tools_javac11_test_windows//:WORKSPACE",
-        "@remote_java_tools_javac14_test_darwin//:WORKSPACE",
-        "@remote_java_tools_javac14_test_linux//:WORKSPACE",
-        "@remote_java_tools_javac14_test_windows//:WORKSPACE",
         "@remote_java_tools_linux_for_testing//:WORKSPACE",
         "@remote_java_tools_windows_for_testing//:WORKSPACE",
         "@remotejdk11_linux_aarch64_for_testing//:WORKSPACE",