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/code/code-signing.rst

@@ -68,7 +68,7 @@ In the example below, we will use ``keyserver.ubuntu.com``.
 
 Replace 6E2F4E7AF50A5827 with your key ID, preferably the **long keyID** which is the last 16 hex digits of the long number in the second line of the output above:
 
-.. code:: bash
+.. code:: text
 
       pub   rsa3072 2021-12-30 [SC] [expires: 2023-12-30]
             87975838063F97A968D503266E2F4E7AF50A5827
@@ -89,7 +89,7 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
 
 1. Set up Git to use your key:
 
-   .. code:: bash
+   .. code:: console
 
          git config --global user.signingkey <KEYID>
 
@@ -97,14 +97,14 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
 
 2. Set up Git to sign your commits with your key:
 
-   .. code:: bash
+   .. code:: console
 
          git config --global commit.gpgsign true
 
 
    Alternatively, manually specify when a commit is to be signed:
 
-   .. code:: bash
+   .. code:: console
 
          git commit -S
 
@@ -114,14 +114,14 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
 
    This is useful for example, if you have a commit back in the git history which you like to sign now without rewriting the history.
 
-   .. code:: bash
+   .. code:: console
 
          git tag -s <tag_name> -m "<tag_message>"
 
 
    You can also create an alias to make this easier. Edit your ``~/.gitconfig`` file. In the ``[alias]`` section, add ``stag`` to create signed tags and ``spush`` to create signed tags and push them.
 
-   .. code:: bash
+   .. code:: ini
 
          [alias]
          stag = "!bash -c 'id=\"`git rev-parse --verify HEAD`\"; tag_name="signed_tag_for_${id:0:8}"; git tag -s "$tag_name" -m \"Tag for commit $id\"; echo \"$tag_name\"'"
@@ -130,7 +130,7 @@ If you’re submitting a patch via GitHub (or a similar Git server), please sign
 
    You may also find it convenient to have an alias for verifying the tag on the latest commit:
 
-   .. code:: bash
+   .. code:: console
 
          vtag = !git tag -v `git describe`
 
@@ -170,14 +170,14 @@ In this case, you have several options to sign the commit:
 
 1. Amend the commit and replace it with a signed commit. You can use this command to create a new signed commit:
 
-   .. code:: bash
+   .. code:: console
 
          git commit --amend -S
 
 
    This also rewrites the commit so you need to push it forcefully:
 
-   .. code:: bash
+   .. code:: console
 
          git push -f
 
@@ -185,7 +185,7 @@ In this case, you have several options to sign the commit:
 
 2. Create a signed tag for the unsigned commit. If the commit is back in history and you do not want to change it, you can create a signed tag for this commit and push the signature. You can use the alias from above:
 
-   .. code:: bash
+   .. code:: console
 
          git checkout <commit>
          git spush

developer/code/source-code.rst

@@ -19,7 +19,7 @@ All of our repositories are available under the `QubesOS GitHub account <https:/
 
 To clone a repository:
 
-.. code:: bash
+.. code:: console
 
       git clone https://github.com/QubesOS/qubes-<repo_name>.git <repo_name>
 
@@ -27,7 +27,7 @@ To clone a repository:
 
 e.g.:
 
-.. code:: bash
+.. code:: console
 
       git clone https://github.com/QubesOS/qubes-core-admin.git core-admin
 
@@ -37,7 +37,7 @@ To build Qubes you do not need to download all these repositories. If you use :d
 
 If you really do want to clone **all** of the repositories, you can use these commands:
 
-.. code:: bash
+.. code:: console
 
       curl "https://api.github.com/orgs/QubesOS/repos?page=1&per_page=100" | grep -e 'clone_url*' | cut -d \" -f 4 | xargs -L1 git clone
       curl "https://api.github.com/orgs/QubesOS/repos?page=2&per_page=100" | grep -e 'clone_url*' | cut -d \" -f 4 | xargs -L1 git clone
@@ -46,7 +46,7 @@ If you really do want to clone **all** of the repositories, you can use these co
 
 To update (git fetch) **all** of these repositories :
 
-.. code:: bash
+.. code:: console
 
       find . -mindepth 1 -maxdepth 1 -type d -exec git -C {} fetch --tags --recurse-submodules=on-demand --all \;