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.

1993/rince/design.md

@@ -10,10 +10,9 @@ For instance, assume you wish to make a boulder `o` roll off a hill `/`
 A standard automata would have 2 rules something like this:
 
 ```
-
-		o..			...
-		\..  -->  'o'		.o.  -->  '.'
-		...			.\.
+    o..			...
+    \..  -->  'o'		.o.  -->  '.'
+    ...			.\.
 ```
 
 However, the system I devised, in order to keep things small and neat(!),
@@ -21,9 +20,9 @@ was to define a 3x3 to 3x3 map (instead of the 3x3 to 1x1 shown above).
 Hence:
 
 ```
-	.o.	  ...
-	.\.  -->  .\o
-	...	  ...
+    .o.	  ...
+    .\.  -->  .\o
+    ...	  ...
 ```
 
 This does of course have the odd problem with clashes. What if we want to roll
@@ -33,9 +32,9 @@ transition has priority win. Such a case may produce the following change of
 maps (depending on which 'roll' transition is used first).
 
 ```
-	o.o			..o	    o..
-	\./	changes to	\o/  or to  \o/
-	...			...	    ...
+    o.o			..o	    o..
+    \./	  changes to	\o/  or to  \o/
+    ...			...	    ...
 ```
 
 I claim that it is possible to perform all of the 3x3 to 1x1 transitions in a
@@ -60,9 +59,9 @@ is hit we have a transition like:
 ## Key: l
 
 ```
-	* * *		* * *
-	* @ .		* . @
-	* * *		* * *
+    * * *		* * *
+    * @ .		* . @
+    * * *		* * *
 ```
 
 Here I also use wildcards. On the match side (left) of the transition, an
@@ -74,9 +73,9 @@ purposes of space saving, this transition is shrunk to a single line.
 ## Key: K
 
 ```
-	a b c		1 2 3
-	d e f		4 5 6
-	g h i		7 8 9
+    a b c		1 2 3
+    d e f		4 5 6
+    g h i		7 8 9
 ```
 
 is written as: `eabcdfghi512346789K`.
@@ -87,8 +86,8 @@ the following (angle brackets denote an 'entity' to be defined):
 
 
 ```
-	<top-bot transition>*\n<bot-top transition>*\n<X size>[ \t]+<Y size>\n
-	<map>
+    <top-bot transition>*\n<bot-top transition>*\n<X size>[ \t]+<Y size>\n
+    <map>
 ```
 
 The `<X size>` should take into account the newline at the end of each line