chore: revert ReadConfig function

[jmeridth]

• replaced fmt logging with message, key/value pair logging format
• revert ReadConfig function as it causes the log to not be read initially
• fixed trace output of config (write directory and invasive were reversed)

I tested this inside the generated plugin and also from the core level. Having the CORRECT config is the fix. Not a code change.

Example new output of config trace:

config.yml

logLevel: trace
write-directory: test_output
services:
  my-cloud-services1:
    plugin: example
    test-suites:
      # - tlp_red
      # - tlp_amber
      - tlp_green
      - tlp_clear

Service name NOT provided

➜  privateer git:(main) ✗ ./privateer run
2025-01-19T03:56:45.775-0600 [TRACE] Creating a new config instance for service: serviceName=overview loglevel=trace write-directory=/Users/jmeridth/.privateer/logs/2025-01-19T035645-0600 invasive=false test-suites=[] vars=map[] writing output to file=true

Service name provided

➜  privateer git:(main) ✗ ./privateer run --service my-cloud-services1
2025-01-19T04:01:44.149-0600 [TRACE] Creating a new config instance for service: serviceName=my-cloud-services1 loglevel=trace write-directory=/Users/jmeridth/.privateer/logs/2025-01-19T040144-0600 invasive=false test-suites=["tlp_green", "tlp_clear"] vars=map[] writing output to file=true

Want to get this merged before I finish my work on #50

[jmeridth]

@eddie-knight I don't know if you feel strongly about logs being newlined or not. Willing to remove that change if necessary.

I realized my issues were I still had writeDirectory in my config.yml. It needed to be write-directory.

[jmeridth]

Once this release happens, I'll do a quick follow-up PR in core and remove the ReadConfig call there.

[eddie-knight]

Ran locally to confirm expected behavior with privateer and with "debug" on a plugin— everything works as expected. Thanks for this @jmeridth