Correct code-block lexers

Changing `bash` lexer to `console` because it is appropriate most of
the time. Then after a manual review, some lexer have been changed.

I used `text` each time I was unsure, and for prompt outputs.

The page `/developer/building/qubes-iso-building.rst` still need to be
reviewed (look for lines starting with `$ #`).

I'm not sure about the Windows pages, should we use
[doscon](https://pygments.org/docs/lexers/#pygments.lexers.shell.MSDOSSessionLexer)
or `powershell`?

Is there an appropriate lexer for `guid.conf` content?

**Statistics - Before**
    870 bash
      9 python
      9 c
      2 yaml

**Statistics - After**
    684 console
    111 text
     44 bash
     16 yaml
      9 systemd
      9 c
      8 python
      4 ini
      4 doscon
      2 markdown
      2 desktop
      1 xorg.conf
      1 xml+jinja
      1 xml
      1 kconfig
      1 html

This suggests that the default lexer should be `console`.

developer/debugging/windows-debugging.rst

@@ -45,9 +45,9 @@ You will need to create a custom libvirt config for the target VM. See `the docu
 
 
 
-.. code:: bash
+.. code:: xml+jinja
+
 
-      
       {% extends 'libvirt/xen.xml' %}
       {% block network %}
          <interface type='ethernet'>
@@ -58,7 +58,7 @@ You will need to create a custom libvirt config for the target VM. See `the docu
             <model type='e1000' />
          </interface>
       {% endblock %}
-      
+
 
 
 
@@ -98,7 +98,7 @@ Host and target preparation
 
   - ``kdnet`` should show that the NIC is supported, note the busparams:
 
-    .. code:: bash
+    .. code:: text
 
           Network debugging is supported on the following NICs:
           busparams=0.6.0, Intel(R) PRO/1000 MT Network Connection, KDNET is running on this NIC.
@@ -117,7 +117,7 @@ Host and target preparation
 
 - Reboot ``target-vm``, debugging should start:
 
-  .. code:: bash
+  .. code:: text
 
         Waiting to reconnect...
         Connected to target 10.137.0.19 on port 50000 on local IP 10.137.0.20.