fix: disable automaxprocs logging

[nitishfy]

Closes #20066

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[bunnyshell]

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[bunnyshell]

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 7 lines in your changes missing coverage. Please review.

Project coverage is 55.96%. Comparing base (5f8de97) to head (9c23436).
Report is 53 commits behind head on master.

Files with missing lines	Patch %	Lines
cmd/main.go	28.57%	5 Missing ⚠️
cmd/util/app.go	71.42%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #20069      +/-   ##
==========================================
+ Coverage   55.95%   55.96%   +0.01%     
==========================================
  Files         322      322              
  Lines       44544    44715     +171     
==========================================
+ Hits        24923    25024     +101     
- Misses      17055    17101      +46     
- Partials     2566     2590      +24     

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

[reggie-k]

I think that it is useful to log the GOMAXPROCS after it was auto-set by the automaxprocs.
The reason is that now, when using automaxprocs, it's value would probably be changed for pods, and when investigating resource consumption / performance issues, it might be important to know what it was set to.
Since the error for local environments / argocd cli commands is obviously annoying, disabling the default logging like you did, makes total sense, and I suggest to add an explicit DEBUG-level log for CPU and GOMAXPROCS values similarly to here afterwards:
uber-go/automaxprocs#18 (comment)
Then it can be tested on both cli commands and argocd container startups to see whether acceptable.
WDYT? I am definitely open to other opinions :)

[gdsoumya]

@reggie-k that's a good point, we can try something like maxprocs.Set(maxprocs.Logger(log.Debugf)) @nitishfy

[nitishfy]

@agaudreault can you review the PR now?

[nitishfy]

@agaudreault PTAL!

[gdsoumya]

/cherry-pick release-2.13

[pasha-codefresh]

/cherry-pick release-2.13