Machinery for Daemon to write setup values to config.toml

[kauri-hero]

Currently we don't utilize the config.toml feature to store and maintain the daemon setup parameter values for Node. This allows persistent daemon setup to remain between environment restarts.

Design and implement ability for the daemon to write and maintain a local config.toml in the data-directory for each chain, so setup parameter values can be persisted in the user environment.

Considerations:

• The --db-password of course should not be written to the config.toml
• Consider how to handle the creation of the initial config.toml when Node is first run on a clean system. Do we keep current defaults, change them for current state of public users (which does have new default for base-sepolia, rather than polygon-mainnet) etc