Don't use nova_console_type for mapping

This causes a circular resolution, as in os_nova role
nova_console_type is calculated based of nova_console_type_mapping.

It was written like that to ensure that defined
nova_console_type will be respected when overriden.

With that change operators need to control
`nova_console_type_mapping` instead of `nova_console_type` to use spice
instead of vnc.

Needed-By: https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/967052
Change-Id: I25f57b450c0642400a4dce729e0cc66b28cf976e
Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>

inventory/group_vars/all/nova.yml

@@ -25,7 +25,7 @@ nova_serialconsoleproxy_port: 6083
 
 # Default nova console proxy types
 nova_console_type_mapping:
-  x86_64: "{{ nova_console_type | default('novnc') }}"
+  x86_64: novnc
   ppc64le: novnc
   aarch64: serialconsole
   disabled: disabled

releasenotes/notes/console_type_mapping-494aadc1f0ac9533.yaml

@@ -0,0 +1,17 @@
+---
+upgrade:
+  - |
+    In order to configure SPICE frontend/backend on the loadbalancer use
+    ``nova_console_type_mapping`` instead of ``nova_console_type``.
+
+    For example:
+
+    .. code-block:: yaml
+
+      nova_console_type_mapping:
+        x86_64: spice
+        ppc64le: novnc
+        aarch64: serialconsole
+
+    Variable ``nova_console_type`` is compute-specific and is not used to
+    calculate configuration for the Load Balancer.