fix: respect log level settings

[wd]

This is an approach to fix #903

However, there are still some info level logs printed.

time="2024-10-31T08:51:43Z" level=info msg=Trace args="[git config user.name argocd]" dir=/tmp/git-rainmaker3532605552 operation_name="exec git" time_ms=1.117718

These logs are generated by codes listed below

1. https://github.com/argoproj-labs/argocd-image-updater/blob/master/ext/git/client.go#L814
2. https://github.com/argoproj/argo-cd/blob/master/util/exec/exec.go#L54
3. https://github.com/argoproj/gitops-engine/blob/master/pkg/utils/tracing/logging.go#L43

They provided a way to set the log level, which is here https://github.com/argoproj/argo-cd/blob/master/util/log/logrus.go#L55. We can use the environment variable ARGOCD_LOG_LEVEL to set the log level. This can be done through the helm chart.

Update:
I test with set below for the helm chart, and it works.

extraEnv:
  - name: ARGOCD_LOG_LEVEL
    value: "warn"

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.84%. Comparing base (e09b17d) to head (49c3dbd).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #904      +/-   ##
==========================================
+ Coverage   74.82%   74.84%   +0.01%     
==========================================
  Files          31       31              
  Lines        3912     3915       +3     
==========================================
+ Hits         2927     2930       +3     
  Misses        850      850              
  Partials      135      135              

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

[jannfis]

Nice! Can you please fix the DCO by signing off your commit?

[wd]

@jannfis Done. I fixed the CI.

[jannfis]

LGTM, thanks!