[hotfix] We want site_has_own_route to be a Boolean

We are not entirely sure why this was working before. But if a `>` multi-line indicator is used, the final newline in the quoted multi-line string is kept; resulting in something that Ansible is well within its rights to refuse to interpret as a Boolean. As a consequence, the `when: site_has_own_route` guard in `ansible/roles/wordpress-instance/tasks/routes.yml` was always true, resulting in spurious attempts to apply the `oc` command (which doesn't - yet? - exist in the ansible-runner image).

Author: Dominique Quatravaux

ansible/roles/wordpress-instance/vars/routes-vars.yml

@@ -3,7 +3,7 @@ route_is_root_url: '{{ lookup("wpveritas", "url") is match("https?://[^/]+$") }}
 route_hostname: '{{ lookup("wpveritas", "url") | hostname_of_url }}'
 route_name: '{{ lookup("wpveritas", "url") | route_name(route_wp_veritas_env) }}'
 site_exists: '{{ not lookup("wpveritas", "isDeleted") }}'
-site_has_own_route: >
+site_has_own_route: >-
     {{ route_wp_veritas_env.startswith("unm-")
     or route_wp_veritas_env.startswith("subdomains")
     or (openshift_namespace == "wwp-test" and route_is_root_url) }}