feat: tools-2777 associate validation errors with the config section that caused…

[dwelch-spike]

… them
Note: tools-2885 was found while working on this PR so I fixed it in c0dfad6 . The issue caused the output of the validate command to go to stderr.

I ended up backing the tools-2885 changes out.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 91.54930% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 78.79%. Comparing base (d694a4a) to head (c0dfad6).
Report is 1 commits behind head on main.

Files	Patch %	Lines
conf/config_validator.go	91.42%	4 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
+ Coverage   77.87%   78.79%   +0.91%     
==========================================
  Files          14       14              
  Lines         940     1009      +69     
==========================================
+ Hits          732      795      +63     
- Misses        141      145       +4     
- Partials       67       69       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dwelch-spike]

I found that the validation failures the validate command prints were actually going to stderr not stdout. They should be going to stdout. I filed a bug ticket https://aerospike.atlassian.net/browse/TOOLS-2885, since it was a 1 line change I fixed the issue in c0dfad6 . Just changing cmd.Print to fmt.Print does the trick.

[jdogmcsteezy]

LGTM after TOOLS-2885 is backed out

[dwelch-spike]

tools-2885 is backed out, waiting for tests to pass then will merge