improved indentation and whitespace for markdown code blocks

All code blocks in markdown have been intended by at least 4 spaces.

We add `--tab-stop=8` to all `pandoc(1)` executions in order to set
a better tab stop indentation, especially for tab intended code blocks.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.5.3 2024-03-26"
to "1.6 2024-03-31".

Fixed `1991/brnstnd/sorta.README.md` so that the sorta code
is code blocks.

Removed unneeded paragraph group in copyright in `inc/footer.default.html`.

Fixed excess whitespace after list Author on entry `index.html` page.

Changed `bin/output-index-author.sh` VERSION from "1.5.2 2024-03-26"
to "1.6 2024-03-31".

Performed `make www` to perform the above and test under macOS.

TODO: Fix the problem of the initial line of code being extra intended.
TODO: Fix excess whitespace around code that is inline.

1995/garry/README.md

@@ -1,21 +1,21 @@
 ## To build:
 
 ```sh
-make all
+    make all
 ```
 
 
 ## To use:
 
 ```sh
-./garry <input_file >output_file
+    ./garry <input_file >output_file
 ```
 
 
 ## Try:
 
 ```sh
-./try.sh
+    ./try.sh
 ```
 
 
@@ -30,21 +30,21 @@ left intact) looked very much like a rat "dropping core".  See
 ### Alternate build:
 
 ```sh
-make alt
+    make alt
 ```
 
 
 ### Alternate use:
 
 ```sh
-./garry.alt <input_file >output_file
+    ./garry.alt <input_file >output_file
 ```
 
 
 ### Alternate try:
 
 ```sh
-./try.alt.sh
+    ./try.alt.sh
 ```
 
 
@@ -64,13 +64,13 @@ The calling syntax is pretty simple, just use it with `stdio`-redirection
 or inside pipelines, e.g.:
 
 ```sh
-./garry <file_to_convert >converted_file
+    ./garry <file_to_convert >converted_file
 ```
 
 or
 
 ```sh
-cat all_my_files/* | ./garry | lp
+    cat all_my_files/* | ./garry | lp
 ```
 
 The syntax of the conversion of the input file is as follows: To include the
@@ -78,8 +78,8 @@ value of an environment variable in the output file, place the name of the
 variable between `$`-signs in the input, e.g.:
 
 ```
-My Home-Directory is: $HOME$
-I'm using the path: $PATH$
+    My Home-Directory is: $HOME$
+    I'm using the path: $PATH$
 ```
 
 Unknown Env-variables or malformed expressions are ignored and kept intact.
@@ -88,10 +88,10 @@ Additionally, the filter replaces escaped octal values in the environment
 variables by their binary representation, e.g.:
 
 ```sh
-$ TEST="\110\145\154\154\157"
-$ export TEST
-$ echo '$TEST$' | ./garry
-Hello
+    $ TEST="\110\145\154\154\157"
+    $ export TEST
+    $ echo '$TEST$' | ./garry
+    Hello
 ```