Revert "ANDROID: GKI: enable CONFIG_TLS=m as a GKI module"

This reverts commit 1b5a5cb71d.

CONFIG_TLS introduces and unacceptable attack surface.  Since it was
enabled in December 2024, we have received an influx of security reports
which have been directly attributable to the aforementioned commit.  To
ensure a greater level of system integrity going forward, we are
disabling its use completely.

BoringSSL remains the sole approved implementation of TLS in Android.
Current users of CONFIG_TLS should convert their workflows back over to
BoringSSL immediately.

Bug: 459542688
Change-Id: Ifb828e6fcb7f8fda75a50a3338dbdafe6c9de4a7
Signed-off-by: Lee Jones <joneslee@google.com>

arch/arm64/configs/gki_defconfig

@@ -136,7 +136,6 @@ CONFIG_LRU_GEN=y
 CONFIG_LRU_GEN_ENABLED=y
 CONFIG_NET=y
 CONFIG_PACKET=y
-CONFIG_TLS=m
 CONFIG_XFRM_USER=y
 CONFIG_XFRM_INTERFACE=y
 CONFIG_XFRM_MIGRATE=y

arch/x86/configs/gki_defconfig

@@ -133,7 +133,6 @@ CONFIG_LRU_GEN=y
 CONFIG_LRU_GEN_ENABLED=y
 CONFIG_NET=y
 CONFIG_PACKET=y
-CONFIG_TLS=m
 CONFIG_XFRM_USER=y
 CONFIG_XFRM_INTERFACE=y
 CONFIG_XFRM_MIGRATE=y

bazel/modules_private.bzl

@@ -87,7 +87,6 @@ _COMMON_GKI_MODULES_LIST = [
     "net/rfkill/rfkill.ko",
     "net/tipc/tipc.ko",
     "net/tipc/tipc_diag.ko",
-    "net/tls/tls.ko",
     "net/vmw_vsock/vmw_vsock_virtio_transport.ko",
 ]