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.

2018/algmyr/README.md

@@ -1,7 +1,7 @@
 ## To build:
 
 ```sh
-make
+    make
 ```
 
 To use this entry requires, in some invocations, a sound processing program.
@@ -14,7 +14,7 @@ compile and use an IOCCC entry that requires sound?](../../faq.html#sox).
 The current status of this entry is:
 
 ```
-STATUS: INABIAF - please **DO NOT** fix
+    STATUS: INABIAF - please **DO NOT** fix
 ```
 
 For more detailed information see [2018 algmyr bugs](../../bugs.html#2018_algmyr).
@@ -23,16 +23,16 @@ For more detailed information see [2018 algmyr bugs](../../bugs.html#2018_algmyr
 ## To use:
 
 ```sh
-./prog < prog.c			# Print garbage: might mess up your terminal
-./prog <file1> <file2> > out.raw
-./prog -d 2 0 out.raw		# Decode the first (0th) channel out of two
+    ./prog < prog.c			# Print garbage: might mess up your terminal
+    ./prog <file1> <file2> > out.raw
+    ./prog -d 2 0 out.raw		# Decode the first (0th) channel out of two
 ```
 
 
 ## Try:
 
 ```sh
-./try.sh
+    ./try.sh
 ```
 
 
@@ -165,13 +165,13 @@ standards compliant). This is used to print the usage instructions.
 Compiling using
 
 ```sh
-gcc -Wall -Wextra -pedantic
+    gcc -Wall -Wextra -pedantic
 ```
 
 gives only `-Wmisleading-indentation` which is sensible considering the source code. While
 
 ```sh
-clang -Wall -Wextra -pedantic
+    clang -Wall -Wextra -pedantic
 ```
 
 is a bit more pessimistic and gives `-Wempty-body` (I like loops without
@@ -180,7 +180,7 @@ concatenation) and one of the weirder warnings I have seen from me splitting a
 negative constant with whitespace. Compiling using
 
 ```sh
-clang -Wall -Wextra -pedantic -Weverything
+    clang -Wall -Wextra -pedantic -Weverything
 ```
 
 produces a few page faults of warnings and makes me feel generally bad about