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`.

introduction/faq.rst

@@ -231,8 +231,8 @@ Which virtualization modes do VMs use?
 
 Here is an overview of the VM virtualization modes:
 
-.. list-table:: 
-   :widths: 42 42 
+.. list-table::
+   :widths: 42 42
    :align: center
    :header-rows: 1
 
@@ -248,7 +248,7 @@ Here is an overview of the VM virtualization modes:
      - PV
    * - Stub domains - HVMs
      - PV
-   
+
 
 
 What's so special about Qubes' GUI virtualization?
@@ -543,7 +543,7 @@ or
 
 - Go to the sysfs (``/sys/bus/pci``), find the right device, detach it from the pciback driver and attach back to the original driver. Replace ``<BDF>`` with your device, for example ``00:1c.2``:
 
-  .. code:: bash
+  .. code:: console
 
         echo 0000:<BDF> > /sys/bus/pci/drivers/pciback/unbind
         MODALIAS=`cat /sys/bus/pci/devices/0000:<BDF>/modalias`
@@ -672,7 +672,7 @@ I see a screen popup with SeaBios and 4 lines, last one being ``Probing EDD (edd
 
 From a ``dom0`` prompt, enter:
 
-.. code:: bash
+.. code:: console
 
       qvm-prefs <HVMname> kernel ""
 
@@ -696,7 +696,7 @@ I see a "Failed to start Load Kernel Modules" message on boot
 
 The full message looks like:
 
-.. code:: bash
+.. code:: text
 
       [FAILED] Failed to start Load Kernel Modules.
       See 'systemctl status systemd-modules-load.service' for details.
@@ -834,4 +834,4 @@ Is there a way to automate tasks for continuous integration or DevOps?
 Yes, Qubes natively supports automation via :doc:`Salt (SaltStack) </user/advanced-topics/salt>`. There is also the unofficial `ansible-qubes toolkit <https://github.com/Rudd-O/ansible-qubes>`__. (**Warning:** Since this is an external project that has not been reviewed or endorsed by the Qubes team, `allowing it to manage dom0 may be a security risk <https://forum.qubes-os.org/t/19075#dom0-precautions>`__.)
 
 .. |checkmark| image:: /attachment/doc/checkmark.png
-.. |redx| image:: /attachment/doc/red_x.png
+.. |redx| image:: /attachment/doc/red_x.png

introduction/issue-tracking.rst

@@ -207,13 +207,13 @@ Use collapsible sections for long, nonessential content
 
 On GitHub, create collapsible sections in Markdown like so:
 
-.. code:: bash
+.. code:: html
 
       <details>
       <summary>Summary goes here. This line is optional.</summary>
-      
+
       Long, nonessential content goes here. You can put a code block here, but make sure to leave empty lines before and after the fence lines (```).
-      
+
       </details>
 
 

introduction/statistics.rst

@@ -36,7 +36,7 @@ How are Tor users counted?
 
 We estimate the number of Tor users as a proportion of the total number of *requests* from Tor exit nodes on the assumption that the proportion of users to requests is roughly the same for both clearnet and Tor users. To be precise, the formula is:
 
-.. code:: bash
+.. code:: text
 
       tor_users = tor_requests * (plain_users / plain_requests)