docs: fix invalid transport_socket value (#9403)

Signed-off-by: Derek Argueta <dereka@pinterest.com>

Mirrored from https://github.com/envoyproxy/envoy @ 7114dcd71080bec8603896f916b077d00da91c0a

envoy/api/v2/cds.proto

@@ -487,12 +487,12 @@ message Cluster {
   //    match:
   //      acceptMTLS: true
   //    transport_socket:
-  //      name: tls
+  //      name: envoy.transport_sockets.tls
   //      config: { ... } # tls socket configuration
   //  - name: "defaultToPlaintext"
   //    match: {}
   //    transport_socket:
-  //      name: "rawbuffer"
+  //      name: envoy.transport_sockets.raw_buffer
   //
   // Connections to the endpoints whose metadata value under *envoy.transport_socket*
   // having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.

envoy/api/v3alpha/cds.proto

@@ -522,12 +522,12 @@ message Cluster {
   //    match:
   //      acceptMTLS: true
   //    transport_socket:
-  //      name: tls
+  //      name: envoy.transport_sockets.tls
   //      config: { ... } # tls socket configuration
   //  - name: "defaultToPlaintext"
   //    match: {}
   //    transport_socket:
-  //      name: "rawbuffer"
+  //      name: envoy.transport_sockets.raw_buffer
   //
   // Connections to the endpoints whose metadata value under *envoy.transport_socket*
   // having "acceptMTLS"/"true" key/value pair use the "enableMTLS" socket configuration.