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/releases/1_0/release-notes.rst

@@ -17,7 +17,7 @@ Known issues
 
 - On systems with more than 8GB of RAM there is problem with DisposableVM. To fix it, limit maximum memory allocation for DispVM to 3GB
 
-  .. code:: bash
+  .. code:: console
 
         qvm-prefs -s fedora-17-x64-dvm maxmem 3072
         qvm-create-default-dvm --default-template --default-script
@@ -56,7 +56,7 @@ From Qubes 1.0 Beta 3
 
 If you have Qubes Beta 3 currently installed on your system, you must reinstall from scratch, as we offer no direct upgrade option in the installer (sorry). However, we do offer tools for smooth migration of your AppVMs. In order to do that, please backup your AppVMs using the ``qvm-backup`` tool :doc:`as usual </user/how-to-guides/how-to-back-up-restore-and-migrate>`. Then, after you install Qubes 1.0 rc1, you can restore them using ``qvm-backup-restore`` tool. However, because we have changed the default template in RC1, you should tell qvm-back-restore about that by passing ``--replace-template`` option:
 
-.. code:: bash
+.. code:: console
 
       qvm-backup-restore <backup_dir> --replace-template=fedora-15-x64:fedora-17-x64
 

developer/releases/4_0/release-notes.rst

@@ -64,7 +64,7 @@ Security Notes
 
   3. In the window that opens, enter this command:
 
-     .. code:: bash
+     .. code:: console
 
            sudo nano /etc/yum.repos.d/qubes-dom0.repo
 
@@ -85,10 +85,10 @@ Security Notes
 
   3. In the window that opens, enter the command for your version:
 
-     .. code:: bash
+     .. code:: console
 
-           [Qubes 3.2] sudo gedit /etc/yum.repos.d/qubes-r3.repo
-           [Qubes 4.0] sudo gedit /etc/yum.repos.d/qubes-r4.repo
+           [Qubes 3.2] $ sudo gedit /etc/yum.repos.d/qubes-r3.repo
+           [Qubes 4.0] $ sudo gedit /etc/yum.repos.d/qubes-r4.repo
 
 
 

developer/releases/4_2/release-notes.rst

@@ -91,7 +91,7 @@ Notes
 
   - Users who wish to opt for the more restrictive 4.2.0 and 4.2.1 behavior can do so by modifying their RPC policy rules. To switch a single rule to the more restrictive behavior, change ``*`` in the argument column to ``+`` (i.e., change “any argument” to “only empty”). To use the more restrictive behavior globally, add the following “deny” rule before all other relevant rules:
 
-    .. code:: bash
+    .. code:: text
 
           qubes.Filecopy    +allow-all-names    @anyvm    @anyvm    deny
 
@@ -124,13 +124,13 @@ Upgrading
 Please see :doc:`how to upgrade to Qubes 4.2 </user/downloading-installing-upgrading/upgrade/4_2>`.
 
 .. |Screenshot of the Qubes OS Update tool| image:: /attachment/site/4-2_update.png
-   
+
 
 .. |Screenshot of the Qubes OS Global Config tool| image:: /attachment/site/4-2_global-config_1.png
-   
+
 
 .. |image1| image:: /attachment/site/4-2_global-config_2.png
-   
+
 
 .. |Screenshot of the Qubes OS Policy Editor tool| image:: /attachment/site/4-2_policy-editor.png
-   
+