feat: add EtlConfig as well as setting the directory to datadir (#7124)

Co-authored-by: Mikhail Sozin <mikhail.sozin@chainstack.com>
Co-authored-by: Misha <mikawamp@gmail.com>
Co-authored-by: Alexey Shekhirin <a.shekhirin@gmail.com>

book/cli/reth/recover/storage-tries.md

@@ -41,6 +41,20 @@ Options:
   -h, --help
           Print help (see a summary with '-h')
 
+Database:
+      --db.log-level <LOG_LEVEL>
+          Database logging level. Levels higher than "notice" require a debug build
+
+          Possible values:
+          - fatal:   Enables logging for critical conditions, i.e. assertion failures
+          - error:   Enables logging for error conditions
+          - warn:    Enables logging for warning conditions
+          - notice:  Enables logging for normal but significant condition
+          - verbose: Enables logging for verbose informational
+          - debug:   Enables logging for debug-level messages
+          - trace:   Enables logging for trace debug-level messages
+          - extra:   Enables logging for extra debug-level messages
+
 Logging:
       --log.stdout.format <FORMAT>
           The format to use for logs written to stdout

book/cli/reth/stage/run.md

@@ -62,7 +62,10 @@ Options:
           Batch size for stage execution and unwind
 
       --etl-file-size <ETL_FILE_SIZE>
-          Size for temporary file during ETL stages
+          The maximum size in bytes of data held in memory before being flushed to disk as a file
+
+      --etl-dir <ETL_DIR>
+          Directory where to collect ETL files
 
   -s, --skip-unwind
           Normally, running the stage requires unwinding for stages that already have been run, in order to not rewrite to the same database slots.