Config option changes for refzero torture

config/config-options/DUK_USE_DEBUGGER_TRANSPORT_TORTURE.yaml

@@ -6,6 +6,7 @@ default: false
 tags:
   - debugger
   - development
+  - torture
 description: >
   Development time option: force debugger transport torture.  Concretely this
   now causes Duktape to read/write debug protocol data in 1-byte increments,

config/config-options/DUK_USE_GC_TORTURE.yaml

@@ -5,6 +5,7 @@ tags:
   - gc
   - memory
   - development
+  - torture
 description: >
   Development time option: force full mark-and-sweep on every allocation to
   stress test memory management.

config/config-options/DUK_USE_REFZERO_FINALIZER_TORTURE.yaml

@@ -0,0 +1,12 @@
+define: DUK_USE_REFZERO_FINALIZER_TORTURE
+introduced: 1.3.0
+default: false
+tags:
+  - gc
+  - memory
+  - development
+  - torture
+description: >
+  Development time option: simulate a fake finalizer call for every object
+  going through refzero freeing.  This is useful to detect bugs caused by
+  finalizer side effects in e.g. call handling.

config/config-options/DUK_USE_SHUFFLE_TORTURE.yaml

@@ -5,6 +5,7 @@ tags:
   - gc
   - memory
   - development
+  - torture
 description: >
   Development time option: force compiler to shuffle every possible opcode
   to stress shuffle behavior which is otherwise difficult to test for

config/tags.yaml

@@ -67,3 +67,9 @@ fastpath:
 
 cstackdepth:
   title: C stack depth
+
+torture:
+  title: Development time torture options
+  description: >
+    Development time options to stress test corner case handling by e.g.
+    causing a garbage collection on every allocation.