A re-encrypt Route with destinationCACertificate explicitly set to the default serviceCA skips internal Service TLS certificate validation

Issue

• A re-encrypt Route with destinationCACertificate explicitly set to the default serviceCA seems to skip internal Service TLS certificate validation, errorless serving content even if target Service certificate and certificate provided by target Pod(s) differ.
• If there is no destinationCACertificate set in the route yaml manifest (the route will still implicitly use the same default serviceCA certificate, as described in the doc about Network APIs / Route) the expected error page will be shown.