Starting delayed_node creates unusable config.ini

[jmjatlanta]

Bug Description
Starting delayed_node with no previous config.ini will create one with all data within duplicated.

Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.

• API (the application programming interface)
• Build (the build process or something prior to compiled code)
• CLI (the command line wallet)
• Deployment (the deployment process after building such as Docker, Travis, etc.)
• DEX (the Decentralized EXchange, market engine, etc.)
• P2P (the peer-to-peer network for transaction/block propagation)
• Performance (system or user efficiency, etc.)
• Protocol (the blockchain logic, consensus, validation, etc.)
• Security (the security of system or user data, etc.)
• UX (the User Experience)
• Other (please add below)

Steps To Reproduce
Start delayed_node with config.ini missing

Expected Behavior
A default config.ini is created that is usable

Screenshots (optional)

~/Development/cpp/bitshares-core/build$ ./programs/delayed_node/delayed_node 
1862781ms th_a       main.cpp:122                  main                 ] Writing new config file at /home/jmjatlanta/Development/cpp/bitshares-core/build/delayed_node_data_dir/config.ini
1862782ms th_a       main.cpp:206                  main                 ] Exiting with error:
13 N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_13property_tree10ini_parser16ini_parser_errorEEEEE: /home/jmjatlanta/Development/cpp/bitshares-core/build/delayed_node_data_dir/config.ini(167): duplicate key name
/home/jmjatlanta/Development/cpp/bitshares-core/build/delayed_node_data_dir/config.ini(167): duplicate key name: 
    {"what":"/home/jmjatlanta/Development/cpp/bitshares-core/build/delayed_node_data_dir/config.ini(167): duplicate key name"}
    th_a  main.cpp:315 load_logging_config_from_ini_file

Host Environment
Please provide details about the host environment. Much of this information can be found running: witness_node --version.

• Host OS: Ubuntu 18.04 LTS
• Host Physical RAM 64GB
• BitShares Version: develop
• OpenSSL Version: 1.1.1
• Boost Version: 1.68

CORE TEAM TASK LIST

• Evaluate / Prioritize Bug Report
• Refine User Stories / Requirements
• Define Test Cases
• Design / Develop Solution
• Perform QA/Testing
• Update Documentation

[jmjatlanta]

Code for delayed_node looks very similar to witness_node, but generates different results. I am still investigating.

[abitmore]

If delayed_node is unusable but nobody complained, I think it's a good time to deprecate it now. People who need the features should run witness_node --plugins delayed_node.

[pmconrad]

I suppose it is still usable in existing installations. New installations hopefully won't use it.
I've left it out of the gitian build, so far nobody has complained.
I've thought about replacing the binary with a wrapper script, but it gets complicated with the "--plugins" option.

[abitmore]

Fixed by #1988.