Add support for JSON log formatting

[mikepilat]

Fixes #436
Fixes #515

• Add log setter for text or JSON log formatting
• Add CLI option "--log-format", accepts "text" or "json"
• Defaults to current "text" logging for compatibility

Additionally:

• Configure cmd go.mod to reference registry-scanner locally to support concurrent changes in both modules

[codecov-commenter]

Codecov Report

❌ Patch coverage is 9.09091% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 63.58%. Comparing base (ded7a28) to head (2b56830).

Files with missing lines	Patch %	Lines
cmd/run.go	9.09%	10 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1231      +/-   ##
==========================================
- Coverage   63.77%   63.58%   -0.19%     
==========================================
  Files          23       23              
  Lines        3213     3224      +11     
==========================================
+ Hits         2049     2050       +1     
- Misses       1054     1064      +10     
  Partials      110      110              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jannfis]

Nice! Thank you.

LGTM.

[jannfis]

Sorry, I was too quick with my approval 😅

Please check my comments.

[chengfang]

According to https://argo-cd.readthedocs.io/en/stable/user-guide/commands/argocd_admin/#options, argocd uses logformat instead of log-format. I think we should probaby follow the existing naming pattern of loglevel (used in both argo-cd and image-updater), and logformat from argocd. The same for the corresponding environmental variable.

[chengfang]

@mikepilat I moved the changes related to registry-scanner replacement into a seprate #1234 since that could also benefit other PRs in the same concurrent update situation. I also took the liberty to resolve the conflicts and pushed to your branch.

Can you please review the remaining comments in this PR so we can include this in the upcoming release?

[mikepilat]

@chengfang Thanks for bringing that upstream! Other PR feedback has been incorporated.