feat(dfns): render blocks and components (#332)

Add component and block rendering methods ss suggested in #311 (comment). Also some DFN snapshot updates.

Author: wpbonelli

autotest/dfns/__snapshots__/v2.0.0.dev0/gwe-adv.json

@@ -10,7 +10,7 @@
       "reader": "urword",
       "optional": true,
       "longname": "advective scheme",
-      "description": "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme.",
+      "description": "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme.",
       "valid": "central upstream tvd"
     },
     "ats_percel": {

autotest/dfns/__snapshots__/v2.0.0.dev0/gwe-adv.toml

@@ -9,7 +9,7 @@ type = "string"
 reader = "urword"
 optional = true
 longname = "advective scheme"
-description = "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme."
+description = "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme."
 valid = "central upstream tvd"
 
 [options.ats_percel]

autotest/dfns/__snapshots__/v2.0.0.dev0/gwe-adv.yaml

@@ -9,8 +9,8 @@ options:
     reader: urword
     optional: true
     longname: advective scheme
-    description: scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified,
-      upstream weighting is the default weighting scheme.
+    description: scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If
+      not specified, upstream weighting is the default weighting scheme.
     valid: central upstream tvd
   ats_percel:
     block: options

autotest/dfns/__snapshots__/v2.0.0.dev0/prt-oc.json

@@ -305,6 +305,14 @@
       "longname": "print particle tracking events",
       "description": "print a verbose particle tracking event trace to standard output",
       "mf6internal": "dev_dump_evtrace"
+    },
+    "scratch_buffer": {
+      "block": "options",
+      "type": "keyword",
+      "reader": "urword",
+      "optional": true,
+      "longname": "buffer track events in scratch file instead of memory",
+      "description": "keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer. Particle tracking results calculated during a time step are buffered, and output is deferred, until successful completion of the time step. By default, results are buffered in memory. However, for simulations in which a very large number of track events is generated during a time step, memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results in a scratch file until successful completion of the time step. Buffering in a scratch file is typically slower than buffering in memory."
     }
   },
   "dimensions": {

autotest/dfns/__snapshots__/v2.0.0.dev0/prt-oc.toml

@@ -293,6 +293,14 @@ longname = "print particle tracking events"
 description = "print a verbose particle tracking event trace to standard output"
 mf6internal = "dev_dump_evtrace"
 
+[options.scratch_buffer]
+block = "options"
+type = "keyword"
+reader = "urword"
+optional = true
+longname = "buffer track events in scratch file instead of memory"
+description = "keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer. Particle tracking results calculated during a time step are buffered, and output is deferred, until successful completion of the time step. By default, results are buffered in memory. However, for simulations in which a very large number of track events is generated during a time step, memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results in a scratch file until successful completion of the time step. Buffering in a scratch file is typically slower than buffering in memory."
+
 [dimensions.ntracktimes]
 block = "dimensions"
 type = "integer"

autotest/dfns/__snapshots__/v2.0.0.dev0/prt-oc.yaml

@@ -281,6 +281,19 @@ options:
     longname: print particle tracking events
     description: print a verbose particle tracking event trace to standard output
     mf6internal: dev_dump_evtrace
+  scratch_buffer:
+    block: options
+    type: keyword
+    reader: urword
+    optional: true
+    longname: buffer track events in scratch file instead of memory
+    description: keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer.
+      Particle tracking results calculated during a time step are buffered, and output is deferred, until
+      successful completion of the time step. By default, results are buffered in memory. However, for
+      simulations in which a very large number of track events is generated during a time step, memory
+      limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results
+      in a scratch file until successful completion of the time step. Buffering in a scratch file is typically
+      slower than buffering in memory.
 dimensions:
   ntracktimes:
     block: dimensions

autotest/dfns/__snapshots__/v2.0.0.dev1/gwe-adv.json

@@ -8,7 +8,7 @@
     "options": {
       "scheme": {
         "block": "options",
-        "description": "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme.",
+        "description": "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme.",
         "valid": "central upstream tvd",
         "reader": "urword",
         "optional": true,

autotest/dfns/__snapshots__/v2.0.0.dev1/gwe-adv.toml

@@ -6,7 +6,7 @@ ftype = "ADV"
 
 [blocks.options.scheme]
 block = "options"
-description = "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme."
+description = "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme."
 valid = "central upstream tvd"
 reader = "urword"
 optional = true

autotest/dfns/__snapshots__/v2.0.0.dev1/gwe-adv.yaml

@@ -7,8 +7,8 @@ blocks:
   options:
     scheme:
       block: options
-      description: scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not
-        specified, upstream weighting is the default weighting scheme.
+      description: scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If
+        not specified, upstream weighting is the default weighting scheme.
       valid: central upstream tvd
       reader: urword
       optional: true

autotest/dfns/__snapshots__/v2.0.0.dev1/prt-oc.json

@@ -264,6 +264,14 @@
         "mf6internal": "dev_dump_evtrace",
         "longname": "print particle tracking events",
         "type": "keyword"
+      },
+      "scratch_buffer": {
+        "block": "options",
+        "description": "keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer. Particle tracking results calculated during a time step are buffered, and output is deferred, until successful completion of the time step. By default, results are buffered in memory. However, for simulations in which a very large number of track events is generated during a time step, memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results in a scratch file until successful completion of the time step. Buffering in a scratch file is typically slower than buffering in memory.",
+        "reader": "urword",
+        "optional": true,
+        "longname": "buffer track events in scratch file instead of memory",
+        "type": "keyword"
       }
     },
     "dimensions": {