docs code block formatting

`console` type code-block is designed mainly for examples of the console commands with the output.

If it's just a shell script with comments, then `console` only gets in the way - e.g. if you try to select a console code block manually, you won't be able to select comment symbol `#` at the beginning of the command making code unrunnable if you try to copy and run it. I've replaced it with `bash` or `bat` (for Windows) code blocks where `console` wasn't necessary.

I've also removed `$` symbols at the beginning of the commands if it's not a `console` code-block - since otherwise it just breaks "Copy Code Block" because you copy unrunnable code.

src/ifcopenshell-python/docs/ifcsverchok/installation.rst

@@ -71,23 +71,23 @@ Just symbolically link the IfcSverchok add-on files to your Git repository. If
 you're on Windows, use ``mklink`` instead. This allows us to code in our Git
 repository, and see the changes in our Blender installation.
 
-::
+.. code-block:: bash
 
-    $ git clone https://github.com/IfcOpenShell/IfcOpenShell.git
-    $ cd IfcOpenShell
+    git clone https://github.com/IfcOpenShell/IfcOpenShell.git
+    cd IfcOpenShell
 
     # Link the repository to blender
-    $ ln -s src/ifcsverchok /path/to/blender/2.XX/scripts/addons/ifcsverchok
+    ln -s src/ifcsverchok /path/to/blender/2.XX/scripts/addons/ifcsverchok
     
 On Windows:
 
-::
+.. code-block:: bat
 
-    $ git clone https://github.com/IfcOpenShell/IfcOpenShell.git
-    $ cd IfcOpenShell
+    git clone https://github.com/IfcOpenShell/IfcOpenShell.git
+    cd IfcOpenShell
 
     # Link the repository to blender
-    $ mklink /D "\path\to\blender\2.XX\scripts\addons\ifcsverchok" "\path\to\src\ifcsverchok"
+    mklink /D "\path\to\blender\2.XX\scripts\addons\ifcsverchok" "\path\to\src\ifcsverchok"
 
 After you modify your code in the Git repository, you will need to restart
 Blender for the changes to take effect. In ``Edit > Preferences > Add-ons`` you