Remove invalid TLS setting

OTP 26 no longer ignores `fail_if_no_peer_cert` for a `client` setting.
Instead, distributed Erlang fails without informative error messages.

See the following issues:

* erlang/otp#7497
* rabbitmq/rabbitmq-website#1687

`customize_hostname_check` is client only

Author: lukebakken

docs/examples/mtls-inter-node/inter_node_tls.config

@@ -5,20 +5,16 @@
     {keyfile,    "/etc/rabbitmq/certs/tls.key"},
     {secure_renegotiate, true},
     {fail_if_no_peer_cert, true},
-    {verify, verify_peer},
-    {customize_hostname_check, [
-      {match_fun, public_key:pkix_verify_hostname_match_fun(https)}
-    ]}
+    {verify, verify_peer}
   ]},
   {client, [
     {cacertfile, "/etc/rabbitmq/certs/ca.crt"},
     {certfile,   "/etc/rabbitmq/certs/tls.crt"},
     {keyfile,    "/etc/rabbitmq/certs/tls.key"},
     {secure_renegotiate, true},
-    {fail_if_no_peer_cert, true},
     {verify, verify_peer},
     {customize_hostname_check, [
       {match_fun, public_key:pkix_verify_hostname_match_fun(https)}
     ]}
   ]}
-].
+].