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.

2005/mynx/README.md

@@ -1,7 +1,7 @@
 ## To build:
 
 ```sh
-make
+    make
 ```
 
 There is an alternate version that scans for (_ONLY_ scans) the string `https`
@@ -13,7 +13,7 @@ as a starting point. See [alternate code](#alternate-code) below.
 The current status of this entry is:
 
 ```
-STATUS: INABIAF - please **DO NOT** fix
+    STATUS: INABIAF - please **DO NOT** fix
 ```
 
 For more detailed information see [2005 mynx bugs](../../bugs.html#2005_mynx).
@@ -22,7 +22,7 @@ For more detailed information see [2005 mynx bugs](../../bugs.html#2005_mynx).
 ## To use:
 
 ```sh
-./mynx http://<domain>
+    ./mynx http://<domain>
 ```
 
 You can specify a port by appending to the domain `:port`. See notes below on
@@ -32,9 +32,9 @@ the issue of https.
 ## Try:
 
 ```sh
-./mynx http://www.textfiles.com
+    ./mynx http://www.textfiles.com
 
-./mynx manual.html
+    ./mynx manual.html
 ```
 
 
@@ -59,7 +59,7 @@ must just appreciate the entry for what it once was.
 ### Alternate build:
 
 ```sh
-make alt
+    make alt
 ```
 
 
@@ -69,7 +69,7 @@ Use `mynx.alt` as you would `mynx`. You'd have to specify a port at the end of
 the URL like:
 
 ```sh
-./mynx.alt https://www.ioccc.org:443
+    ./mynx.alt https://www.ioccc.org:443
 ```
 
 but again unless you have a clever workaround or hack to the problem, this sadly
@@ -93,13 +93,13 @@ it inspired me to try my hand at writing the client side complement.
 A typical build command would be:
 
 ```sh
-cc -o mynx mynx.c
+    cc -o mynx mynx.c
 ```
 
 While some others like to be a little different:
 
 ```sh
-cc -o mynx mynx.c -lnsl -lsocket
+    cc -o mynx mynx.c -lnsl -lsocket
 ```
 
 I even managed to figure out a basic configure script, given last year's
@@ -108,13 +108,13 @@ all the network functions in a variety of places. So a simpler build
 command sequence would be:
 
 ```sh
-cd source ; ./configure ; make
+    cd source ; ./configure ; make
 ```
 
 After which, the rest of the documentation can be read by saying:
 
 ```sh
-./mynx ../manual.html
+    ./mynx ../manual.html
 ```