Generate reference config from previous logs

[alexandraBara]

Scope: Use previous node-scraper logs to generate a reference config by parsing the log files.
node-scraper --gen-reference-config-from-logs <path_to_previous_logs>

Sample run:

node-scraper --gen-reference-config-from-logs scraper_logs_TheraC56_2025_07_07-11_11_08_AM/

Sample output:

$ node-scraper --gen-reference-config-from-logs scraper_logs_TheraC56_2025_07_07-11_11_08_AM/
  2025-07-07 14:13:41 CDT       INFO               nodescraper | Log path: ./scraper_logs_2025_07_07-02_13_41_PM
  2025-07-07 14:13:41 CDT       INFO               nodescraper | Reference config written to: /home/alexbara/node-scraper/reference_config.json

reference_config.json:

{
  "global_args": {},
  "plugins": {
    "BiosPlugin": {
      "analysis_args": {
        "exp_bios_version": [
          "M17"
        ],
        "regex_match": false
      }
    },
    "OsPlugin": {
      "analysis_args": {
        "exp_os": [
          "8.10"
        ],
        "exact_match": true
      }
    }
  },
  "result_collators": {}

README.md updates to follow

[bargajda-amd]

@alexandraBara have you checked if reference config file generated directly (--gen-reference-config) is identical to one generated from logs, assuming same "input" node?

[alexandraBara]

@alexandraBara have you checked if reference config file generated directly (--gen-reference-config) is identical to one generated from logs, assuming same "input" node?

I have not, let me investigate

[alexandraBara]

@alexandraBara have you checked if reference config file generated directly (--gen-reference-config) is identical to one generated from logs, assuming same "input" node?

I have not, let me investigate

The end files are the same. We will be adding this test to functional testing in the future to make sure it stays that way.

[landrews-amd]

Looks good! added a couple suggestions

[landrews-amd]

Should remove the 'Writes to ./reference_config.json.' part since we are now leveraging the output path arg