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.

2004/omoikane/README.md

@@ -1,21 +1,21 @@
 ## To build:
 
 ```sh
-make
+    make
 ```
 
 
 ## To use:
 
 ```sh
-./omoikane infile layout outfile
+    ./omoikane infile layout outfile
 ```
 
 
 ## Try:
 
 ```
-./try.sh
+    ./try.sh
 ```
 
 
@@ -44,7 +44,7 @@ insert a human-readable checksum string in the text itself!  `^_^`
 ### Usage
 
 ```sh
-./omoikane <infile> <layout> <outfile>
+    ./omoikane <infile> <layout> <outfile>
 ```
 
 All three arguments may reference the same file.  All files is
@@ -82,18 +82,18 @@ layout.
 Example file/layout:
 
 ```
-file:                layout:
-   crc = ########       ... . XXXXXXXX
-   patch = ######       ..... . XXXXXX
-   other text here      ..... .... ....
+    file:                layout:
+       crc = ########       ... . XXXXXXXX
+       patch = ######       ..... . XXXXXX
+       other text here      ..... .... ....
 ```
 
 And `Rinia` may generate a file similar to this:
 
 ```
-crc = 1bad73cf
-patch = #FR-QQ
-other text here
+    crc = 1bad73cf
+    patch = #FR-QQ
+    other text here
 ```
 
 Note that the original file by itself is a valid layout file, since
@@ -116,9 +116,8 @@ runs faster if the checksum is placed before the other marker
 characters rather than after, e.g.:
 
 ```
- a: X X XXX      b: XXXXXXXX     c: XXXXXXXX
-    XXXXXXXX        X X XXX         XXXXX
-
+    a: X X XXX      b: XXXXXXXX     c: XXXXXXXX
+       XXXXXXXX        X X XXX         XXXXX
 ```
 
 `a` usually takes the longest time, while `c` usually is the