make self-check of /.well-known/matrix/server accept redirects

Rationale: the /.well-known/matrix/client should return only 200 as well, but it has hardcoded "safe" value, regardless the spec: https://spec.matrix.org/v1.4/client-server-api/#well-known-uri

So, why not do the same for the /.well-known/matrix/server?

roles/matrix-nginx-proxy/defaults/main.yml

@@ -489,9 +489,9 @@ matrix_nginx_proxy_self_check_validate_certificates: true
 
 # Controls whether redirects will be followed when checking the `/.well-known/matrix/client` resource.
 #
-# As per the spec (https://matrix.org/docs/spec/client_server/r0.6.0#well-known-uri), it shouldn't be,
-# so we default to not following redirects as well.
-matrix_nginx_proxy_self_check_well_known_matrix_client_follow_redirects: none
+# As per the spec (https://spec.matrix.org/v1.4/client-server-api/#well-known-uri), it shouldn't be,
+# but in real life all client apps and servers accept the 301 redirect.
+matrix_nginx_proxy_self_check_well_known_matrix_client_follow_redirects: safe
 
 # For OCSP purposes, we need to define a resolver at the `server{}` level or `http{}` level (we do the latter).
 #