[ecs] [request]: service connect envoy log spam

As of the date of opening this issue the logs generated by anything with service connect enabled are being spammed with the following envoy deprecation warning. is there any way to silence these? with app mesh we change the envoy log level to error via env vars but im guessing that is no longer possible with service connect?

```
[source/common/protobuf/message_validator_impl.cc:21] Deprecated field: type envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext Using deprecated option 'envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext.match_subject_alt_names' from file common.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/version_history/version_history for details. If continued use of this field is absolutely necessary, see https://www.envoyproxy.io/docs/envoy/latest/configuration/operations/runtime#using-runtime-overrides-for-deprecated-features for how to apply a temporary and highly discouraged override.
```

Start with the reported Envoy warning from source/common/protobuf/message_validator_impl.cc:21 and the referenced common.proto deprecation, then review the linked Envoy runtime-override documentation. Determine whether ECS Service Connect exposes a supported way to change Envoy logging or remove the deprecated configuration; done means the warning no longer spams Service Connect logs without breaking connectivity.

Written by the indexing model from the issue text.