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/general/usability-ux.rst

@@ -153,7 +153,7 @@ By using the same term throughout an interface, a user can create a mental model
 
 It is easy to add words like ``Domain`` before items in a list or menu in an attempt to be descriptive, such as:
 
-.. code:: bash
+.. code:: text
 
       Menu
       - Domain: work
@@ -168,7 +168,7 @@ The repeated use of the word ``Domain`` requires a user to read it for each item
 
 It is more efficient to group things under headings instead as this allows the eye to easily scan the uniqueness of the items. (As per our previous example:)
 
-.. code:: bash
+.. code:: text
 
       Domains
       - Work
@@ -304,4 +304,4 @@ Learning to make well designing intuitive interfaces and software is specialized
 
 
 .. |checkmark| image:: /attachment/doc/checkmark.png
-.. |redx| image:: /attachment/doc/red_x.png
+.. |redx| image:: /attachment/doc/red_x.png